Create condition table for account determination

I would like to create a condition table which contains customer number as the key. However, I can only find the follow fields in field catalog.
Acct Key
AcctAsgnmt
AcctAssgGr
Cond. Type
Distr. Chl
Division
Ord. reason
Plant
Sales org.
Tax Code
Vendor
Is it possible to extend the field catalog? I have tried to added fields in KOMG according to note 21040, but it seems not work.

Hi
some additional information:
please check the documentation under customizing path:
IMG -> Sales and Distribution -> System Modifications ->
Create New Fields (Using Condition Technique) ->
New Fields For Account Determination
click on the icon
Notice that the userexits USEREXIT_ACCOUNT_PREP_KOMKCV and
USEREXIT_ACCOUNT_PREP_KOMPCV are useful only for revenue
account determination.
For reconciliation account determination you should use the userexit
EXIT_SAPLV60B_011 (enhancement SDVFX011) to fill the custom field.
The System modification documentation exaplins to add the new field
in the structure include KOMKCZ of KOMPCZ.
Notice that KOMKCZ is included in KOMKCV and KOMCV; KOMPCZ is included
in KOMPCV and KOMCV.
regards,
Ramana

Similar Messages

Condition table for account determination

Hi,
I would like to know if there is any generic transaction to create condition tables.
Specifically, I would like to create a condition table for revenue account determination.
Any help would be appreciated.
Thanks,
Aroop

Aroop,
Yes you can create IMG --> SD --> BF --> Revenue Account determination --> Define dependencies of revenue account determination --> Account determination create Tables OR Tcode V/12.
Try to create Table above 500 number.
Regards
Sathya

Own condition tables for tax determination purposes

Hi,
While using TAXINN pricing procedure. For simplified tax rate determination, we want to create our own condition tables for tax determination purposes, as is otherwise possible with the conditions technique.
The existing conditions which are pre-delivered with access sequence/s are as:-
TABLE     Description
3     Tax Classification
363     Plant/Vendor/Material
358     Country/Plant/Ctrl code/Material
357     Country/Plant/Ctrl code
362     Country/NBM-NCM Code
359     Plant/Matl group
However we want to create a custom table (9xx:Vendor/Material) with which can meet our requirement of tax determination while purchasing materials.
Could you please elaborate weather our requirement can be fulfilled by standard customization?
Thanking you.
PP

hi sam,
Thanks for reply. I watched many posts related to this issue and your reply is generic one.
I understand that all kind of requirement can be meet with existing data.
I am writing here because I want to reduce the number of records to be maintained. (say, Plant/Vendor/Material, if I have 10 Plants then no of records will be 10 different Plants x vendor x Mat. codes. Hence I am keen to have as Vendor/Mat. code. SAP delivered Plant/Matl group somehow not fulfilling our business need).
I am interested to know weather it is possible to create a custom condition table to meet our requirement/s?
What is your opinion on this..? Please share if you know any SAP Note as am unable to find any relevant one.
Thanks,
PP

Field catalog not appearing in the condition table for output determination

Hello,
I wanted to include WBSTK as a condition table entry in the output determination for outbound deliveries, WBSTK is available as field catalog , but not available during condition table creation.
Can you pls help me out?
Regards
Vaidee

Check OSS Notes
379619 - Preference process in SD order: Prefrnc ID missing
595984 - Preference indicator in SD order
379269 - Preference in SD doc: User exit: Set pref. indicator PREFE
Regards

Create condition table V/57

Hi all,
I'm trying to create a new condition table for output determination and need it to be based on the Sales office, and the customer account group KTOKD.
However, the field KTOKD is not available as an allowed field when creating the condition table.
Can anyone tell me if it is possible to add extra fields into the allowed fields list in V/57 so that I can include the customer account group?
many thanks
Phil

Hi Shiva,
thank you for responding so quickly. We have added the field KTOKD into the structure and activated it as per the note. However, when I modify the access sequence and add in the new condition table, I get the error VT510 "Select a document field for KTOKD".
The system is asking me to assign a document field to the newly added field, when I click on the "field catalogue" button at the bottom a list of fields is displayed and the Customer Account group is not an option.
Thanks again for your help
Regards
Phil

What is the purpose of the release status in creating condition table

hi gurus,
can you please tell me the purpose of the release status and validity date in creating condition table for pricing?
thanks,
Paul

Dear John
The release status controls in which scenarios the condition records are found.
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.
The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status.
thanks
G. Lakshmipathi

Transaction key for account determination

Hi guru,
i would like to add a new transaction key for account determination to fullfil a business process .
Could you help me to find out the Transaction code in customizing?
A prompt reply is appreciated.
Thanks in advance
Vir

Dear Vir,
The G/L account determination process in G/L Accounting mostly uses the
transaction key technique to obtain the required G/L accounts for business transactions.
For Foreign currency transactions:
SPRO -> Financial Accounting -> General Ledger Accounting -> Periodic Processing -> Valuate -> Foreign Currency Valuation
Other General Ledger Transactions
SPRO -> Financial Accounting -> General Ledger Accounting -> Business Transactions -> Closing -> Carried Forward -> Define Retained Earning Account
OBA1 G/L account determination for foreign currency valuation
OBYA Maintain inter-company clearing G/L accounts
OB53 Maintain retained earnings accounts
OBBV Assign AR/AP adjustment accounts
OBXD Maintain bad debt reserve accounts
ACACAD Accrual account determination ( simple or extended )
ACACADMETASGL Accrual account determination strategy
ACACTREE01 Create accrual objects
Pricing:
        V/09    Condition Types: Account Determin.
        V/10    Account Determination: Access Seqnc
        V/11    Conditions: Account Determin.Proced.
        V/12    Account Determination: Create Table
        V/13    Account Determination: Change Table
        V/14    Account Determination: Display Table
G/L Accounts in MM Account Determination:
The program RM07C030 check all the G/L account define in your Material Master valuation class.
Search is via Company code and Valuation area.
Visit the following link for more information:
http://www.sapscene.com/sapscene/accassg.html#SD-FI%20Account%20Determination
Reward points if this is helpful.
Regards,
Naveen.

Posting keys for account determination for transaction EXC do not exist

hi
i am doing Sales order for 1 month,no error i have got
but now i am getting error
Posting keys for account determination for transaction EXD do not exist
HELP

There will not be any such postings called FI side / SD Side.
Positng always done in Financial perspective only into Certain G/L accounts depends on configuration we did.
As we know,
To post Invoice Conditions in G/L accounts , we configure Account Determination . These tables will be communicated through Account keys maintained in Pricing procedure & in Account determination tables.
To account the stock in Inventory, will configure the same in OBYC - FI/MM Account Determination.- this will be triggered through Movement type - Transaction key / General modifier / Valuation calss / Valution group code n other factors.
In your issue,
Which Postings you are referring to?
In SO creation, Controlling documents will be created ( Ref: COPA - Controlling & Profitablity Analysis Customization)
After PGI in Delivery: Inventory will accounted through OBYC settings
After releasing invoice to Accounting, G/L accounts posted through VKOA settings.
Hope ,now you provide exact information related to your query

Sales Order Unable to Use New Condition Tables for Tax Condition Type

Dear All,
I am currently working on SAP R/3 4.0. I have a new requirement for my tax where I need to create new condition tables other than the 4 standard SAP tables which are Customer/Material, Division/Customer, Departure Country/Destination Country, Domestic Taxes and Export Taxes. My new tables consists of Departure Country/Destination Country/Shipping Point/Tax Code. The requirement is that the tax code is based on the chosen destination country and shipping point. The problem I am facing now is that no matter what types of table I create or even I generate with reference to the standard table, the access sequence will only refer to the 4 standard SAP tables above. Even if I put my own table in the highest priority for the access sequence, the same thing happens. My sales order will only pick up date from the standard table.
I wonder if anyone encountered the same problem as me.
Kindly advise.
Thank you.
Regards,
Yvonne

Hi
Yvonne
I suggest fist check a simple thing ,whether u have successfully determined shipping point for each line item ,it is possible that just adding a line item will not trigger shipping point determination . So after u update the shipping point on line level u can rerun pricing and check agian if u r getting it .
Secondly for tax purposes I suggest Try to have Customer and material tax classification approach this allows to u have long term flexibiliy and also reduces your maintenance activity . As if u change or add number of shipping points and business changes using the sequence of shipping point ,the logic of just using shipping point will not work.
In Tax classification u cna add new condition table for each new tax category and use it in different access sequences.
This information can be passed on to FI using Different Tax code for Different combination.
I hope this helps
Regards
Mandar

New Condition TAble for Inbound Delivery

Hello
i want to maintain a new Condition table for the Inbound delivery picking with the combination of _Delivery type/Plant
so that the Inbound created for the particular plant alone uses the particular output type.
Where in IMG can i configure the new Condition table for this combination for the Inbound delivery ?

Hi,
Go to SPRO > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output Determination for Inbound Deliveries > Here perform following;
- Define Condition Table for Inbound Delivery
- Define Output Types for Inbound Delivery
- Define Access Sequence for Inbound Delivery
- Maintain Output Determination Procedure
- Assign Output Determination Procedures

Error in :Posting keys for account determination

Hi, Gurus,
      please suggest the solution for the following problem.
            we are selling two types of materials, one is the product material and the second one is the scrap material.Different type pricing procedures, sale order,delivery and billing types were configured for the same. For CST and VAT   same condition type :"ZCST - for CST " and ZVAT - for VAT" were used in both pricing procedure and the standard account keys : MW1 for ZCST and MWS for ZVAT and same G/L accounts configured .
.                                                   key combination for the condition types as mentioned below:
.                                                        ZCST: Country/PlntRegion/Region/TaxCl2Cust/TaxCl.2Mat
                                                         ZVAT: Country/PlntRegion/Region/TaxCl1Cust/TaxCl.Mat
     Now we want to capture CST and VAT seperately for both the materails.For that two new account keys created and incorporated the same in scrap pricing procedure and and new G/Ls created and assigned .Now the system is throwing following error while while releasing the billing document to accounting document.
Posting keys for account determination for transaction Z48 do not exist
Message no. F5598
here Z48 is the new accounting key created for the CST tax.We tried all the possibilities, but system is throwing the same error.
with regards
sam

Thank u for ur response.Now it is solved when OB40 and OBCN maintained.Here I am facing a new problem.pl. provide the solution.we configured twoseperate pricing procedures for our product and scrap material.We have configured same condition types for VAT(ie.condition type:ZVAT) and CST(cond type:ZCST), in both pricing procedures. Now We want to maintain seperate condition types for VAT and CST for pricing procedure for Product material and Scrap material. I have created two new condition types for scrap sales ZSCT- cst for scrap and ZSVT-vat for scrap by copying the same from existing conditions ZCST & ZVAT, and the same is included in the scrap pricing procedure. And also maintained OB40,OBCN,OVK1,OVK3,OVK4, FTXP,FV11 and VK11.
now I am facing the following problems.
1. while creating the Material master & customer master, in tax category sub screen all conditions i.e. conditions defined for product material( ZCST,ZVAT) and defined for scrap material (ZSCT, ZSVT) displaying and these are compulsory fields.
2. While creating the sale order for scrap material, system is considering the TAX classes from ZVAT/ ZCST (defined for product material) and taking the condition value from the condition type ZSVT/ ZSCT with the TAX class values of ZVAT/ZCST.
Now I would like to know is there any procedure to assign the Material type and Customer group to Tax category.
Thanks & Regards
sam

Error in VF02 (Posting keys for account determination for transaction JTS)

Hi,
I have created new account key JTS and also assigned G/L account in VKOA, But at the time of releasing the billing document to accounting, I am getting the below error;
Posting keys for account determination for transaction JTS do not exist
Message no. F5598

Hi Amanulla,
once we create the Account key in revenue determination we have to assign that account key to respective procedure and condition types.
check that.
please award points.
ravikanth

Posting keys for account determination for transaction ERS do not exist

Dear All,
When I try to create an accounting document for a billing document, the below error happened:
Posting keys for account determination for transaction ERS do not exist.
Could any one of you meet the issue before and give me some advice? Thanks a lot.
Ray

Dear,
In your pricing procedure check whether any sales deductions / discounts condition type is maintained and against that maintain ERS account key.
and Go to VKOA and maintain gl account against your Kofi and KOFK for account key ERS.
try and let us know
regards,
SUdhir

Posting keys for account determination

Hi all
I'll try to post an sales ticket from Retail modul to SD module.
I have this message error : Posting keys for account determination for transaction ZST do not exist
Message no. F5598
Diagnosis
The posting keys necessary for account determination for transaction Z
    have not been set.
System Response
Because the posting key is missing, the system cannot generate any
    automatic postings.
Procedure
Maintain the posting keys necessary for transaction ZST.
In VKOA transaction, I check and for me the account determination has been set.
So I was wondering what's goes wrong with this.
Appreciate your expert advise..

HI,
Please check wther In the pricing procedure ZXXX some conditions have account key ZXX.
But in table T030B there is not any record with KTOSL = ZXX.
Check note 1273471,1128659
Regards
Ravinagh Boni

Add fields in fieldctlg in Create condition table in SPRO

Hi Experts,
How can we add more fields in fieldCatlg table which appears in 'Create Condition Table' in Sales Distribution head in SPRO.
Please Suggest.
Rajiv Ranjan

Hi Rajiv
Please go through this extract from documentation:
Creating New Data Fields in a Communication Structure
Data fields are created in the Data Dictionary. You create data elements and fields in the Data Dictionary as well as integrate them in the relevant structures. Use following check list when you create new data fields:
1. Check whether an identical data field already exists in the standard system
If you want to use the order reason (AUGRU) for pricing, for example,
the data element already exists.
If you want to use parts of the product hierarchy, for example, you must create a new data element (e.g. ZZPRODH1).
Remember that new data fields must begin with the letter "ZZ" or "YY" because SAP has selected this name convention to protect modifications of the customer during a release changeover. Create a new domain for the new data element.
If you want to use a new partner function, such as a selling agent (Z1) you have to create a new partner function (Z1) and a new data element (ZZVRTZ1) in Customizing.
2. Using the source tables, check wether the field is used at header or at item level, which determines the structure in which the field is included. The source tables are listed in the section "Supplying Fields Within the Communication Structure and Using Them in Condition Tables" below.
The order reason, for example, is included in table VBAK, the product hierarchy in table VBAP.
3. Integrate the field in the appropriate communication structure by means of an INCLUDE.
For pricing, for example, you include header fields in KOMKAZ, item fields in KOMPAZ: For the field name enter the field description new fields and make sure that they begin with ZZ or YY. For example, enter ZZAUGRU, ZZPRODH, and ZZVRTZ1 and assign them to the SAP data element AUGRU, or the new data elements you have just created ZZPRODH1 and ZZVRTZ1.
The description of the individual functions will inform you about the structures into which the fields must be integrated.
4. Activate the structure.
5. Include a new field in table T681 and allocate it to the application in which is to be used.
Example
A new field for pricing, has the allocation A, V, 001.
When you have succesfully added the new fields in the communication structure, you will be able to find the same in FIELD CATALOG under the acess squences definition. Please check the same...
Regards
Eswar

Create condition table for account determination

Similar Messages

Maybe you are looking for