G/L Account Error While doing Purchase Order In ME21N

Hi,
While Doing Purchase Order in ME21N,i am getting the below error.Kindly help me.
G/L account 809001 cannot be used (please correct)
Message no. ME045
Diagnosis
Comparison of the field selection strings from the G/L account 809001 and the account assignment category F reveals that there is an incompatible combination of field selections for the field selection group 'Network'.
The G/L account field selection is stored in table T004F; that for the account assignment is stored in table T162K.
Procedure
Please enter a correct G/L account.
Thanks
Supriya

Hi Supriya,
U will have to check the field status of account assignment category F in tcode OME9 and compare it with the Field status group that is assigned to GL 809001.
Kindly note that the field status has a prority in the following order.
Supress
Display
Required
Optional
Thus if the network field is suppressed in GL field status and option in account assignment category F, then the below error would come.
Regards,
Kiran

Similar Messages

Getting runtime error while doing sales order

Hi,
I am getting a runtime error while doing sales order.
Error : SAPSQL_INVALID_FIELDNAME
Kindly suggets....stuck up badly.
cant do any transaction.
Regards
Kishan

Hello,
Check OSS Note#209847 and 310304
Regards,
Gauravjit.
Reward points if the notes are helpful

Error while saving purchase order

Hi all,
While saving purchase order i am getting the following error.
Syntax error in program SAPLV61A
in include RV64A932
in line 10
Statement"*&"is not defined.check your spelling.
Thanks& Regards,
Hari.

Hi Hari,
I've just encountered the same problem as you have now in your latest post.
Normally the include that you mentioned is a formula condition value include which you can modify but you probably have
to register this object first on the SAP OSS pages to get an Access key to modify it.
After you've obtained a key launch transaction VOFM and comment out the line "TABLES: VBRK, VBAK".
As you see below SAP did exactly the same thing in several other includes.
Include FV64A582
-> is a formula condition value
    tx VOFM
            -> Formulas
     -> Condition Value
     -> Routine number 582
At line 37 I commented out "TABLES: VBRK, VBAK." which is not used
anyway in this include.
On top of that SAP commented out these definitions in several other
includes: eg. FOICH002, FOICH002, OI_LV61ATOI.
If other persons have comments on this topic please respond/advise.
Hari, inform us if this resolved your problem.
Also reward points if my post aided you in resolving your issue.
Thank you for feedback.
Best regards,
Tom Cockaert.

No posting rules exist for account key while doing purchae order.

Hi SAP Expert,
I have following problem while doing purchae order.
No posting rules exist for account key
Message no. FF714
Diagnosis
No posting rules have been defined for the account key in the tax table in table T007B.
Please give me reply.
Thanks in advance,
Yogesh.

check MM pricing procedure for any condition account key is assigned and for that account key, no GL is configured in OBYC, if it is related to tax condition type OB40.
regs,
ramesh b

Update was terminated while creating purchase order from ME21N

Hi Experts,
We are getting this dump when try to create purchase order from ME21N;
Our system ECC 6.0 and IS-AFS (Apparel & Footwear Solution) V600 component has installed,
How can we prevent this error,
Regards
Here is the dump and sm21 log,
Runtime Errors         LOAD_PROGRAM_NOT_FOUND
Exception              CX_SY_PROGRAM_NOT_FOUND
Date and Time          10.10.2008 10:22:03
Short text
     Program "RMCMS431 " not found.
What happened?
     There are several possibilities:
     Error in the ABAP Application Program
     The current ABAP program "SAPLMCS4" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     or
     Error in the SAP kernel.
     The current ABAP "SAPLMCS4" program had to be terminated because the
     ABAP processor detected an internal system error.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
     caught in
    procedure "TMC2F_FROUT_CALL" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    On account of a branch in the program
    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
    or a transaction call, another ABAP/4 program
    is to be loaded, namely "RMCMS431 ".
    However, program "RMCMS431 " does not exist in the library.
    Possible reasons:
    a) Wrong program name specified in an external PERFORM or
       SUBMIT or, when defining a new transaction, a new
       dialog module or a new function module.
    b) Transport error
How to correct the error
    Check the last transports to the R/3 System.
    Are changes currently being made to the program "SAPLMCS4"?
    Has the correct program been entered in table TSTC for Transaction "ME21N "?
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "LOAD_PROGRAM_NOT_FOUND" "CX_SY_PROGRAM_NOT_FOUND"
    "SAPLMCS4" or "LMCS4F10"
    "TMC2F_FROUT_CALL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "TMC2F_FROUT_CALL" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
sm21 log ;
Transaction Canceled 00 671 ( LOAD_PROGRAM_NOT_FOUND 20081010102203saptest_TET_00 EYUCE 100
Update terminated
> Update key: F39796DD5421F1509233001E0BD601E0
> Update module: MCE_STATISTICS_UPD_V2
Run-time error "LOAD_PROGRAM_NOT_FOUND" occurred

Please follow the oss note 800335
V2 Update terminations in Purchasing transactions after upgrading or installing AFS 5.0 release.
Other terms
AFS, LIS, MIGO, ME22N, OLI3, S433, S431
Reason and Prerequisites
AFS Purchasing infostructure S431 is no longer used. S433 is the valid infostructure for the release AFS 5.0.
Solution
Please do the following.
For customers upgrading to AFS 5.0 only:
> Rebuild Infostructure S433.
- Goto transaction: OLI3 (Statistical Set up of Infostructures)
- Info structure to be compile: S433
- Specify the 'Name of run'.
- Execute.
> Please also follow the instructions given below.
For both Upgrade and Non-upgrade Customers:
> Create the report 'ZDELS431'.
- Transaction: SE38
- Give Program name as ZDELS431.
- Create (F5).
- Title : 'Program to delete S431'.
- Type : 1 (Executable Program).
- Status: T (Test Program).
> Copy the program text from the note and paste in the program.
> Save and activate the program.
> Execute the report for all clients in Update mode.
(Two check-boxes will appear: P_ALL_CL, P_UPDATE.
   Please check both of them).
This report will delete all the references to infostructure S431.

Error while creating purchase order with account assignment category "A"

Dear All,
At the time of creating purchase order with account assignment category A - Asset its throwing error as " GL Account 123400 can not be used"
how to resolve this issue"
Edited by: Matt on Sep 16, 2010 10:09 AM - removed bold tags

HI,
Assign all assets GL to Asset Class
spro --> financial accounting new -->assets accounting --> assets accounting (lean Implementation) --> organization structures --> Assign GL
Hope Help U !
Regards,
Pardeep Malik

G/L account Error while creating Sales Order

Dear Friends,
I was creating the Sales Order with Item Category TAB (Orders in hand). Everything is fine but in the Incompletion Log I am getting error as "G/L Acount".
I have never found this type of error. I tried to figure out the Consumption account determination based on the Acct. Assignment Cat. as "E" in the schedule line categary of "CB". There also everything is fine with Valuation Group and Valuation Class of Material as "3100" etc.
I will be thankful and reward points if anybody helps me in resolving the issue.
Thanka in advance,
Jans

Hi jans
i suppose you are doing an individual purchase order, which has item category group of BANC and item catergory TAB.
As it is an individual purchase order, you need a special stock .
so when you create a sales order VA01 , and try to save , system will show an incompletion log to assign a G/L account .
so go to -> item data -> account assignment - > click on settlement rule
in settlement rule , enter the G/L account (preferrablly a separate G/L account for revenues )
Now you save the order.
let me know the status
Regards
Srinath

Error while cancel Purchase Order

Hello everyone.
I'm trying to cancel a Purchase Order which has a Purchase Delivery Note.
First I cancel the Purchase Delivery Note and than I try to cancel the Purchase Order, but I'm having the following error: "The requested action is not supported for this object."
If I manually cancel the Purchase Delivery Note, I can successfully cancel the Purchase Order by code.
Here is the code I'm using:
Documents lDocumento = Globals.AddOn.ConexaoAuxiliar.GetBusinessObject(BoObjectTypes.oPurchaseDeliveryNotes);
lDocumento.GetByKey("DocEntry");//DocEntry is just an example
Documents lCancelamento = lDocumento.CreateCancellationDocument();
if (lCancelamento.Add() != 0)
     throw new Exception(Globals.AddOn.ConexaoAuxiliar.GetLastErrorDescription());
Then I try to cancel the Purchase Order:
Documents lDocumento = Globals.AddOn.ConexaoAuxiliar.GetBusinessObject(BoObjectTypes.oPurchaseOrders);
lDocumento.GetByKey("DocEntry");//just an example..
if (lDocumento.Cancel() != 0)//if can't cancel, try to close
     if (lDocumento.Close() != 0)//if can't close, show error..
          throw new Exception(Globals.AddOn.ConexaoAuxiliar.GetLastErrorDescription());
SAP 9 PL 10

Hi Leandro,
Sorry, I missed that bit. But that brings to mind, you create the cancellation document, but apparently you do not explicitly cancel the purchase delivery note.
Could you please test that ? So for example:
if (lCancelamento.Add() != 0)
if (lDocumento.Close() != 0)
//etc.
Could you also please test commenting out the code that closes the purchase order, and then check from the B1 client that the delivery was closed and linked to a Returns document ?
Regards,
Johan

Error while transferring Purchase Order from ECC to SUS

we are working on plan driven procurement and transferring the PO from ECC to SUS, we are getting the error as "No partner found for partner number ECCSUS8".
In ECC the Vendor No is ECCSUS8, trasfered vendor from ECC to SUS. Vendor registration is done based on the mail generated and vendor login is created in the portal and assigned the roles.

Hi
Are you facing this error in PO transmission to SUS (as you mentioned below)? or you are facing this error while sending out the vendors from R/3 to SUS from BD14?
If you are facing this in vendor transmission, you need to remove the tick (flag) "Use self reg component" in SPRO-SRM server-Supplier Self-ServicesMaster DataMake Settings for Business Partners. Then you can transmit the vendors from R/3 succesfully.
If this error is in PO transmission, need to analyse further.
Pls do let me know.
Thanks
Kiran

Error while Changing Purchase Order quantity

Hi experts,
I am doing a BDC so that it should change the invoice quantity by the Received quantity, and also if the received quantity is 0 it should delete that particular Line item. It is doing well for the above, but i am getting stucked in a po number withe following error,
"Quantity delivered differs from qty. invoiced (Function not possible)". Can any one please help me in this issue...
thanks ,
Ajeeth

you can only set a deletion indicator if invoiced quantity and received quantites are equal.
check the PO history in PO item detail , there you can see how much you received and how much was invoiced.
Maybe you missed to clear GR/IR account with MR11

Error while doing production order settlement

Hi frds,
When I am doing the production order settlement, I am getting the following error
" There are no accrued amounts; settlement is not possible".
The status of the order is TECO CNF DLV PRC BASC BCRQ GMPS MANC.
Rajnish

Rajnish,
Please check if there is cost balance for the order, to me it looks like the order is already settled. In the order display mode (CO03) menu bar Goto->Costs->Balance.
If balance exists then the problem may be related to the settlement period used in the Intial screen of transaction KO88. Please check the cost incured period and use the same period as settlement period.
Regards,
Prasobh

Error while posting purchase order invoice in microsoft dynamics ax 2012

Hii friends,
we are getting Excise record type is should not none while tax codes are calculated. but we have selected that Excise record type also we are getting
same error. please help to solve this problem.

Hi Chintan,
But when my functional consultant was able to process same PO, by using the MIRO transaction and he was able reversal the same Invoice..
The Functional Consultant gave me the amount and input details.. (He was able to using the standard transaction MIRO) Which i am hardcoding through the segments which are mandatory.
When i try to do it through the IDOC process, where i am currently hardcording few values in the segments in we19 transaction and execute the same.
Please let me know if there is any other process.
Thanks
Sunil Kumar

Error while creating Purchase order

Hi Experts,
No posting rules exist for account key
Message no. FF714
Diagnosis
No posting rules have been defined for the account key in the tax table in table T007B.
Procedure
Change the tax table, enter an account key already defined for the transaction in question or define the posting rules for a new account key in table T007B.
I have maintained all account keys in Tax Procedure.
Plz let me y this error is coming.

Hello,
Goto T.Code OB40.
Select the account key you have mentioned in your calculation procedure, and give your Chart of accounts.
Then goto 'Rules' Tab and maintain the fields (against tax code or not) against which you want to maintain G/L accounts for tax processing.Save the entries and try the transaction again.
Regards
Gregory Mathews

Error while doing investment order settlement

Dear all,
My client has not settled certain line items in the
previous year for some Investment orders. Now when he
is carrying out settlement (KO88), for the current
period, he is getting error message " AW 624"(first
settle items from the previous year in the previous
year). How can he settle previous years item in the
current year since FI & CO periods are all closed for
prev. year.
The settlement rule is AUC in this case.
Thanks in adv.
Vijaya

Hi
As per note 82514:
If you simply want to settle the unsettled values from the previous year
in the current year, proceed as described in Notes 425601 and 819197. If
settlement for the previous year is no longer possible, due to concluded
fiscal years in FI and CO, or the reporting problems described above
have to be avoided due to settlement in the previous year, settlement in
the current fiscal year is then particularly necessary.
As far as I know, if note 425601 is fully implemented, AW624 should
become editable in OBA5. Could you please check if the coding has been
correctly applied? Especially below steps need to be done manually:
As a prerequisite for Transaction OBA5, you must first of all implement
the program corrections of note 425601 and insert the following
table entries :
o As of Release 4.6: Use Transaction SM31 to include application
       area 'AW' into table V_T100SA.
o Start Transaction SM31 to include the following entry in table
       T100S:
       'Application area    MsgNo    Allowed      Standard   Switch off'
        AW                  624      EWI          E           'X'
Regards
Javier Reviriego

Error in posting purchase order delivery

Hi
I got an error while posting purchase order delivery through Tcode- MIGO
This is the Error Message:
Posting only possible in 2009/04 and 2009/03 in company code XXXX
I checked everything Fiscal year variant,Posting period variant,etc.
And in Tcode- OMSY.
Let me know as early as possible how to solve this issue.
Thanks and Regards,
Deepthi.

Hi Deepthi,
You need to understand that posting periods 3 and 4 does not necessarily mean march and april in SAP.
Check your fiscal year variant for the months which correspond to periods 3 and 4. Then you will be able to solve your problem by yourself.
Open and close periods in FI - OB52
Close periods and open new periods in MM Side - MMPV
Hope this helps you....
Regards,
Sreekanth....

G/L Account Error While doing Purchase Order In ME21N

Similar Messages

Maybe you are looking for