Error in Determine delta posting in CKMLCPAVR

Hi All,
While testing for CKMLCPAVR " determine Delta posting " I haev come across a weird error
Internal error in FORM+/FUNCTION CKMLAVR_CLOSE_SINGLE in position 6 with RC1
Message no. C+099
Before this error I had faced error where systme has asked to update BSD and UMD key in OBYC. I have updated the same. Later I haev faced the above error.
Just for information I am using actual price as well as in configuration i have updated indicator 2 in activate actual costing.
But I changed from 1 to 2 in half way through my testing.
Please, let me know if any of you have come across such error in course of CKMLCPAVR.
Best Regards
Prabhat Kumar

Hi Sarada,
The multilevel price determination is perfectly ok for me. The kind of weird error messages particularly in ML area .... it is really very hard nut to crack..... I am planning to test again in new plant with the same scenarios.. let me test and if I come across the same error .. then need to think of OSS.
ANyway thanks....
Hello All,
If you have any observation on this , then lplease put your thought forward....
Best Regards
Prabhat Kumar

Similar Messages

Error in determining posting key T030B account account key JP5

Dear all,
at the time of MIRO posting error msg comes
error in determining posting key T030B account account key JP5
Pls guide me
Thanls
amin

Hi
Give the Debit as 40 and Credit as 50
To find the GL code, go to FS00 and give ur company code and get the GL code and assign the same OB40
Regards
Prasanna R
Edited by: Prasanna Raju on Jun 25, 2009 12:35 PM
Edited by: Prasanna Raju on Jun 25, 2009 12:36 PM
Edited by: Prasanna Raju on Jun 25, 2009 12:36 PM

Error in determining posting key T030B account key JP7

Hi
While I am running MIRO, following error comes.
Error in determining posting key T030B account key JP7
Message no. FF701
Diagnosis
No posting keys could be found for the account key defined in the tax calculation procedure.
Procedure
Check the following settings in taxes on sales/purchases Customizing.
To do this, choose Maintain entries (F5):
1. Check or correct the calculation procedure.
2. Check whether you have specified a valid transaction key in the tax type used.
If it is a new transaction key, you must first define the posting rules. Enter the transaction keys in the calculation procedure
Can u please advise me where I have to make changes in my config.
Rakesh

Hi ,
this error is coming because transaction key JP7 is not maintained with respect to posting keys .
In SE16 open table T030B and maintain transaction Key JP7 with posting keys then hopfully ur error with get removed.
thanks
deepa

Error in determining posting key T030B account key GT0 Message no. FF701

While doing MIRO i am getting this error
Error in determining posting key T030B account key GT0
Message no. FF701
I dont know y..can u pls help me on this?

Hi
Try this
This error is coming because transaction key GT0 is not maintained with respect to posting keys .
In SE16 open table T030B and maintain transaction Key GT0 with posting keys then hopfully ur error with get removed.
Goto to SE11 put the table name T030B enter then click on change button select transaction type GT0 Maintain Debit 40 & Credit 50.
go to OB40
here find the GT0 key double click on it and then maintain the posting key

Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /

Guyz,
Firstly despite the plant+storage location + warehouse no. assignments are done , my replenishment delivery (delivery for stock transport order between plants under same company code) is not picking up storage location and warehouse no and thus stopping me from doing picking and PGI (post goods issue).
However in VL02N when i'm trying to change storage location for line item, i'm getting following weird error
*Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /*
I found a SAP Note(133223) regarding this error and VL02 transaction but that note was specific to older versions. I'm on ECC 6.0
Any suggestions please ?
Thanks

Warehouse managment has its own movement types, most identical to inventory management movement types.
These WM movement types are determined via reference movement types.
the error you have just looks like your customizing is not complete.
IMG > LE > WM > Interfaces > IM > define movement types.

Error in document date & posting date-- Posting period 001 2008 is not open

hi guru's
while doing vendor creation in XK01, i m not getting the data screens like address, ..etc.i m getting error..posting period not open". what does it mean..
What date i need to give in both fields...?
can anybody send a set of data for me to create a vendor to test for my bdc/lsmw?
can any help me step by step vendor creation in xk01,
I am getting this below....
Posting period 001 2008 is not open
Message no. F5201
Diagnosis
Period 001 of fiscal year 2008 is not open for posting for the variant of posting period 1000.
System Response
Processing cannot be continued.
Procedure
The error can have several causes. In order to eliminate the error, proceed as follows:
1. Check whether the posting date was entered correctly. The system determines the posting period by means of the date.
2. Check whether the required posting period is open for posting for the variant of posting period 1000 and account type +. Make sure that the period is open for posting.
To do this, specify a period interval in which the required period for the variant of posting period 1000 and account type + is contained.
Proceed
thanks

Hi
Kris is right, that message means you can't post a FI document in the period 1 (probably Gennuary) of the 2008, but this can't mean you can't create a new vendor.
So are you sure on trx?
If the trx is right perhaps somebody has inserted a control in a user-exit.
Max

Account determination for posting area Aggr

Hi experts,
i'm very new to ISU and would like your help on an issue.i am using ETHIM to post mass act aggr posting for the serv prov.i get an error *Key selection not defined for application &1, posting area &2* msg no 005..
exact error msg would be *In Customizing, define the keys you require by selecting the appropriate entry for account determination for posting area Aggr.: Conversion of Ext. Transacts. to N(R075).*
what transaction will i have to use in order to post the doc. doc type AL.
thanks in advance
cheers,
deepak rao

hi Deepak,
FQC0 is the correct t.code and maintain the document type for the posting area
BA: payment settlement
SA: GL account document
just try it out with this.
Regds,
Naren

Account determination for posting area "1040

Hi
While creating a check lot we're getting the error as
"In account determination for posting area "1040" (interim account for incoming payments), your specifications are either incomplete or missing.
The transaction affects company code UINF and currency USD."
Any clue about the reason
Regards,

Hi ,
Maintain the interim account for incoming payments through the T.code FQC0.
Regards,
Konakanchi

Error when trying to post interest using FNM1 in Loan Module

Hi,
I am getting error "50 E INTEREST EXP or ZBA CONTRA ACCT cannot be replaced' when positng the interest payment for loan in loan module. The system has posted a planned record and i see it in the cash flow however when posting the planned record it is giving the above error.
Your inputs are greatly appreciated.

check loan posting scheme here:
Spro - SAP Banking - Loans management - Functions - Accounting - Define account determination
Check posting category against debit/credit posting codes and linked GL accounts for your account symbols or post here what you have defined and I couldl see what the problem is

Error when determining the PSA name

I am on BW3.5, trying to load a delta that has been loading for 2+ years with no problems. The load today is getting the error message: "RSAODS 132 Error when determining the PSA name"
I've looked in OSS Notes and there is nothing with this error message. This is CCA Actual data that loads to PSA > ODS > Cube. The PSA load is red and the entry in the ODS is also red. Thanks

Hello Keith,
Not sure just check following, might help.
This might be because of insufficent authorization ( did you changed anything on authorization company wide decision?)
Or this might be brcause of insufficent tablespace or something?
Sarhan.

Reverse GR error:Account determination for entry GCOA...not possible

Hi!
If we encounter the error Account determination for entry GCOA PRD 0002 ___ ZRO1 not possible when reversing GR, does this have something to do with the number of available stocks of the materials?
In our other servers, the transaction key PRD is blank. but we ca reverse GRs.. but in our production server, PRD is also blank but we cannot reverse the GR. The error Account determination for entry GCOA PRD 0002 ___ ZRO1 not possible comes up.
What could be the reason for this?
Appreciate your help..thanks so much!
Regards,
Paula

Please specify below:
1. what's the price control for problem material? S or V? And what's the price unit?
Price control is V, price unit is PC
There is no change in PO price.. the price is 40.
2. what's the movement type for the material document posted? What's the quantity
in the material document?
mvt type in GR is 101.. PO qty is 3996 pc and GR qty is 3996 pc.
3. what's the accounting doucment posted during the goods movement. Please list all the lines
in FI document with transaction key information(BSX/WRX...)
89 - BSX
96- WRX
4. what's the current stock/stock value for the problem material, i.e. the stock/stock value before
posting the GR reversal?
current stock is 6,383.000 pc
GR reversal has not been done yet...
Thanks so much for your time..
Regards,
Paula

Error:Account determination for entry 1000 KBS 0001 not possible

Hi all,
i created one project PO account assignment category Q ,with out master data ,material text , material group , i entered W.B.S ,
P.O . created ,while doing GR , i am getting following error Account determination for entry 1000 KBS 0001 not possible
regards
vijju

Dear Viju,
                                                                                The error M8 147(Account determination for entry XXX KBS
not possible)is because of the corresponding entry mismatch in T030
table .For resolving this we need to make a corresponding entry in
transaction OBYC (the menu path in SPRO is as follows)
Materials Management
-> Valuation and Account Assignment
   -> Account Determination
      -> Account Determination Without Wizard
         -> Configure Automatic Postings
Please also review
Note 364570 M8147,KBS posting when assigning accnt to GR for PO
Regards
V V

MIGO error price determination

Hi All,
When i post MIGO transaction I get this error.
"Transaction cannot be posted due to errors price determination".
Actualy before this I have some changes in Schedulling Agreement price. So plz tell me where is problem in S.A. or MIGO and what is the problem.
Can anybody help me to resolve this issue.
Thanks in Advance
Jitendra

Hi,
The error is due to the changes in Schedulling Agreement price . Please find the related notes here
1) 113856
2) 447374
3) 456691 'FAQ's
These are all old notes. But you will get an idea.
Hope this helps you.
Regards,

Asking account determination while posting to MB1A

hi friends,
while posting goods issue to cost center(MB1A). i am getting the following error
ACCOUNT DETERMINATION FOR ENTRY (CHART OF ACCOUNTS) GBB _________VBR 3000 NOT POSSIBLE, and
ACCOUNT DETERMINATION FOR ENTRY (CHART OF ACCOUNTS) BSX _________VBR 3000 NOT POSSIBLE
actually i assigned all the required GL acounts in obyc( i assigned GL accounts for BSX and GBB too). i dont know what to do.can anybody please help me out from this problem

OMWB is the right tool to detect the error. Go to this transaction code and enter the plant and material number. Select the movement type (201?). Double click on the GI to cost center. Then click on Account Assignment icon. The resultant output will show what is missing.
Valuation grouping code (Valuation modifier) also plays a majore role, as it groups plant together, to be used in maintaining account determination. of GBB for ZOB

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Error in Determine delta posting in CKMLCPAVR

Similar Messages

Maybe you are looking for