VKOA transaction in PRD

Hi All,
Can anyone please tell why the transaction VKOA in production environment is modifiable even after setting the PRD client as non modifiable in transaction SE03.
Any guesses????
Thanks
Sridhar

To ensure the objects are non-modifiable, please perform the
following steps:
- Call transaction SOBJ -> Maintain
- Doubleclick on the affected objects, e.g. table C501, C502 etc. (these
are the tables you are maintaining in transaction VKOA)
- Delete the flag 'Current settings'
- Save the entries
After this table OBJH should have the correct entries CURSETTING = blank
for the tables C001 etc. what will make this tables unchangeable in
your productive client.

Similar Messages

Posting transaction key PRD

Good morning,
I should do a little analysis about our G/L accounts definition for transaction key PRD. What I would like to understand is how SAP configures the automatic posting procedure or, in a better way, how SAP determines which transaction keys must be used in a particular situation.
I think that these tables should be involved in the procedure:
T156SC
T156SY
T156X
T156W
Does someone have more information?
Thank you in advance.
Francesco Alborghetti

Dear Francesco,
Go to T.code - OBYC.
Select the posting key - PRD.
Give the concern chart of Account and go inside.
You will see Valuation modification and Valuation class assigned to GL accounts.
If you want to include the movement types into this, you need the Account modifier. If so, click rules,
select the check box of Account modifier also and save the screen first.
Then go into the trasnaction, where you will find the Account modifier will also be included. You can select the correct account modifier which is in turn assigned with the movement type.
Hope this helps.
Reward points if satisfied.
Thanks.
Augustine Ponraj.

Transaction key PRD

Hi!
Is it possible to attach a cost center in the GL account in transaction key PRD?
We put the Miscellaneous GL in the transaction key PRD. The cost center is required in the Misc GL. Is there a way that we can set an automatic Cost Center in transaction key PRD?
Thanks so much.
Regards,
Paula
Edited by: Angela Paula Oquendo on Feb 4, 2010 4:26 AM

hi
firstly u have to assign the GL account to the key PRD in transaction code OBYC
now this gl u have to make it cost element in FS00 (in fs00 chnge mode select gl acct and cick on cost element)
now goto OKB9 here give the assignment of Gl acct to the cost center
regards
kunal

Account grouping/Transaction keys PRD/DIF

Hello Gurus
I have a situation that some MIRO posting are using PRD and some are using DIF transaction keys. For some reason The postings with DIF are not picking up the material thus resulting in putting dummy profit center.
Please advise the difference between PRD and DIF and how these are triggered during MIRO transactions.
Many thanks
MSJ

HI Jayaram/Surabhi
The see what you are saying and it make sense after I read your reply.
The reason that I say that few MIRO postings are using DIF is because the posting key 83 debit and 93 credit are defined in the OBYC for DIF.
So when I looked at the document in the Vendor acct (after I post MIRO), I see the profict center and material missing for posting keys 83 and 93 for some postings.
Wheras I can see the profict center and material for posting keys 86 and 96 for some othe MIRo postings which use these posting keys.
Of course all these postings are generated automatically
So my question is where do I make a setting to have the material and profict center generated for posting keys 83 and 93.
I appreciate your help on this critical issue for me.
Please advise.

Transaction Key PRD or BSX

Hello SAP Guru
   I did MIRO and there is a price vairance of $10, But insted of posting happen to PRD account its happening to BSX , I checked all IMJJ OBYC but not be able to fingure out. Can anybody please help.

Base Unit of Measure LB    US pound     Valuation Category
Currency             USD                Current period       07 2014
Division                                Price determ.
Valuation Class      SSM1
VC: Sales order stk                     Proj. stk val. class
Price Control        V                  Price Unit           1
Moving price         0.24               Standard price       0.00
Total Stock          450                Total Value          108.00
Future price         0.00               Valid from
Previous price       0.00               Last price change
NOt be able to insert pic, so sharing details.

What is 'condition type' in VKOA Transaction used for?

Hi,
Could you kindly explain.
Would be better could explain in Busienss example.
Thank you

Hi,
Condition type is used in the VKOA for account determintaion
G/L account is determined by the condition type say KOFI is used for SD IN condition type KOFI we can set the Input parameter for the condition type it is basically the account determination process for example if a G/L account is to be determine Sales org./AcctAssgGr/AcctAsgnmt/Ord.reason/Acct key then we need to create the condition table for the same & that same conditio table is to assgined in the condition type.
It is same like we maintain the condition records for the various condition types like Price Discount etc.
I hope this will clear your doubt to some extent.
regards,
Pritam

PRD - PRA transaction Key

Dear All,
I hav one doubt regarding transaction key PRD - PRA.
When actually it hits . I think it is used while using goods issue and other movements.
But tell me the functionaly of it.
Also I found in OMJJ for movement type 201,221 posting like
PRD PRA and check box is unticked (a/c assignment)
Why is it so?
Pls clear my doubt.
Thanks in advance.
Regards,
Gitesh

Hi,
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price.
Examples:
Goods receipts against purchase orders (if the PO price differs from the standard price),
Goods issues in respect of which an external amount is entered,
Invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification.
If you use account modification, then you can use this modification.
"PRA for goods issues and other movements "
thanks,
Prashant Rathore.

VKOA Error

Hi,
I am getting one error related to VKOA transaction.
Entry V ANDW does not exist - Check your entry
Message no.00 058
Kindly help me regarding this
Thanks
Supriya

Hi Supriya,
What is the transaction code that you are executing??
Is there any other details in your log??
It looks something to be maintained at view SM30 (TAX_SERVICES) for SD module.
Regards,
Ravi

PRD-Auto Post price differences to different price difference accounts

Dear all,
As I know, in Account Automatic Posting, the transaction key PRD is for Cost price Difference.
If I want to post price differences to different price difference accounts in the case of goods receipts for different cost in purchase orders, How can I configure it?
Example, in PO, there is 2 costs: Freight (F) and Insurance(I) are key in as Condition Type.
I would like to post price difference from F to account XXX, and price difference from I to account YYY.
Can I configure like this?
Thank you very much for your support!
Cao Huy

Hello,
What is price difference.
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price difference in genereal will not trigger for the materials with price control V ( Moving average price) but however
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account
For you example, you have you are having PO with Freight (F) and Insurance(I), these are called pallned delivery costs, not Price difference,
so create two different condition type for Freight and insurance and assign two different G/L accounts for these condition types in account determination.
While posting system will hit perticular G/L acconut.
Regards
Mahesh Naik

SM58 Transaction   Error

Hi Everybody,
All day we are having the problem in the SM58 transaction in PRD environment.
The message thar appear is :
Caller       Function Module               Target System Date       Time     Status Text                                          Transaction ID           Host     Tctn Program
CUA_ECP_400 SUSR_USER_RESPONSE            SMDCLI200     14.06.2010 14:47:12 wrong Name or password               0A090A1904F04C166B1F0BD6 ecc01         SAPMSSY1
Caller       Function Module               Target System Date       Time     Status Text                                          Transaction ID           Host     Tctn Program
CUA_ECP_400 SUSR_USER_RESPONSE            SMDCLI200     14.06.2010 14:47:38 User is locked   0A090A1904F04C166B390BE1 ecc01         SAPMSSY1
We have a CUA configured in the Solution Manager, i already checked that the user
CUA_ECP_400 is not locked   in PRD and Solution Manager.
How can we solve this issue?
What log can i check?
Best Regards,
Fábio Karnik Tchobnian

Dear
Double click on the connection SMDCLI200 in SM58 and check the connection test & authorization test.
The caller entry in SM58 does not equal the user that is used in the actual connection. So most likely you are looking at the wrong user as you mention the user is not locked, the log clearly states the user/pass is incorrect and that after X attempts the user gets locked.
When the authorization test fails, you will have to check the correctness of the password in the RFC definition and if the user is locked on the target system.
Kind regards
Tom

PRD and KDM keys are hitting

Dear All,
After doing MIGO a/c entries are correct for import purchase order.
but KDM and PRD keys are getting hitted and some amount is getting debited to G/L which is assigned to KDM key in OBYC and same amount is getting credited in G/L which is assigned to PRD key in OBYC. Thus effect is zero but i am not able to understand why these keys are hitting as there is no price difference.
please let me know the reason if someone went thru same thing.
Naren.

Dear NArendra
1. Transaction event key KDM will be trigerred when we post invoice first and later on there will be a exchange rate difference occured by the time Goods receipt takes place and also if the material having Standard price control.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
2. Transaction event PRD will trigger on different reasons. Material maintained with price control Standard price and the Price in PO is different . Ple3ase refer SAP std documentation on PRD.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
a. None for goods and invoice receipts against purchase orders
b. PRF for goods receipts against production orders and
c. order settlement
d. PRA for goods issues and other movements
e. PRU for transfer postings (price differences in the case of external amounts)
warm regards
Ramakrishna

Account Determination for entry GCOA PRD not possible

Hi! we encountered this error during Invoice Receipt.   During IR, there is a decimal difference between the Invoice Balance in mir7 (in the upper right) and the PO amount. What we do is we put the the decimall difference in the Unplanned Del Costs under the details tab. But our problem is we encounter the error message Account Determination for entry GCOA PRD not possible.   I read that in the transaction key PRD: Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movement in the negative range, the moving average price is not changed. Instead any price differences are posted to a price difference account.
The material in the PO that we are trying to IR have stocks in the system. My question is how can we know the number of stocks that should be available for us to be able to IR?
How can we also avoid these decimal differences between the IR and PO amount?
Thanks so much and appreciate your help..
Regards,
Paula

first thing
If there is small diffrence in Invoice total amount send my vendor and system calculated value and ther is small diffrence then it shoudl go to small diff account
this account should go in OBYC GCOA DIF hear u can give gl account , and also check if u have stet tolearance limit for this amount
SPRT ==MM == LIV == invoice block == Set Tolerance Limits
in this u set BD for ur company code.
if u do this then u will not require to put that small diffrence in unpland delivery cost.
Account Determination for entry GCOA PRD not possible
in OBYC for ur GCOA click on PRD key
and following should be the entry for ur Material valuation class
general modification      valuation class    gl account
(blank)                              xxxx                    xxxxx
PRA                                  xxxx                     xxxx
PRF                                   xxxx                      xxxx
PRU                                  XXXX                       XXXX
depending on ur posting rule set this
hope ur error will go
My question is how can we know the number of stocks that should be available for us to be able to IR?
when do MIRO or MIR7 system check what is the stock qty availabe at the point of posting
say Stk is 10 and u are posting 15 qty than system calculat the value for 10 and post the amount for 10 as inventory cost and remaning 5 will post to price dif account if ther eis change in rate of PO and invoice received.
hope this helps

Transaction Key PRD_PRA

HI All,
In which scenario OBYC Settings Transaction key PRD--PRA will be used. we did nt activated ML. Still the system is throwing a message at that time of cancellation of production order confirmation "Account determination for entry PRD_PRA valuation class XXXX not possible.
1.For PRD_PRA-- ML Need to activated or not??
2. how PRD-PRA is differ from the PRD
3. in which scenario PRD_PRA will be assigned with GL
Thanks

Hi
In PRD we assign accounts for price difference. It is independent of ML activation and has no relevance to ML.
PRD can be used with/without account modifier. If you use account modifier, you can assign separate account for price differences from purchase order or production order etc.
In particular PRD- PRA is for price difference in case of goods issue.
In your case, since you are cancelling Production confirmation, goods issue is happening for the finished good (presumed it is maintained with price control S and backflush is 'ON' for this)
This is the reason error is showing up.
In normal cases PRA will not picked because goods issue is generally done for raw materials which are maintained with price control V.
Generally PRA can be assigned with the same account as that for normal PPV (purchase price variance) account unless business specifically wants to assign something else.
Hope this helps
Regards
Abhinav

OBYC PRD posting to two different GLs Based on stock or non stock PO

Hi Gurus,
In Account determination OBYC we have provided price difference PRD with a P/L account.
The business however wants to post all Stock PO price differences to an balance sheet account while for Non-stock PO price differences it should post to P/L account. As I understand, I need to provide two different GLs in transaction key PRD account determination based on account arrangement category.
How can we achieve this requirement? Is there a way to use General Modification to fulfill this purpose?

Hi Gurus,
In Account determination OBYC we have provided price difference PRD with a P/L account.
The business however wants to post all Stock PO price differences to an balance sheet account while for Non-stock PO price differences it should post to P/L account. As I understand, I need to provide two different GLs in transaction key PRD account determination based on account arrangement category.
How can we achieve this requirement? Is there a way to use General Modification to fulfill this purpose?

Vf02 error while releasing a billing doc to accounting

Hello All,
I m getting the below mentioned error while releasing a billing doc for a accouting.
I have checked all the settings in vkoa , ob52 and many more and all are set properly, now m not able to track where actually the prob is.
error is: No account is specified in item 0000001004
Message no. F5670
Diagnosis
No account was specified for account type "S" in item "0000001004" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred to item "0000001004" of the FI/CO document.
Points wil be rewarded
Thanks,
SUnny

Hi,
Have you checked what is the determination account determination log ? You can do this by entering in VF02 and select from the menu Environment -> Account Determination Analisys -> Revenue Accounts.
In this log you can see what are posting keys determined from the pricing procedure that should be posted in the FI document and determine very easy in which step the account was not determined.
After that you can maintain the correct account in VKOA transaction.
BR,
Valentin

VKOA transaction in PRD

Similar Messages

Maybe you are looking for