Standard field for Country of Despatch in condition table

Hello All,
I want to created a condition table with Despatching Country, Destination Country, Tax Classificatio of Customer and Tax Classification of Material.
In the allowed fields for selection, I am able to get the field LAND (country of despatch). I have created the condition table and assigned in the access sequence. But when I see the analysis in the sales order this field is picking destination country.
I do not want to include Z field in the KOMK/KOMP struture, I want a standard field. Can anybody hlep me out............
Thanks & Regards,
Sreehari.

At my end, its absolutely right?
TKOMK-ALAND is based on delivering/supplying plant.
If that is not the case, then it is not standard, where TKOMK-ALAND is is not equal to T001W-LAND1.
Take assistance of ABAPer in your team & check whether any enhancement (Program MV45AFZZ, Form USEREXIT_PRICING_PREPARE_TKOMK) is done.
Say, in enhancement sales organization country is used as the country of departure.
Regards
JP

Similar Messages

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

Standard field for Net explosive mass (NEM) for dg documents

Hi,
I have searched standard fields in the material master and dangerous goods master but i can not find a standard field for Net explosive mass (NEM). This value is needed for dangerous goods documents.
Is there anyone that know if there is a standard field for this or do I have to create one myself?
Best regards / Gustav

Hello Gustav
sometimes SAP is saying that Enh.- Apck need to be activated and if you take a "close" look this it is not the case. It is sufficient to use new SPs.
Now based on your reseach results:
Actually the situtation regarding Enh.. Pack is like this:
a.) to use EHS you need to "switch" (activate) the EA-APPL component; no way back ! possible !
b.) to use Enh. Pack EHS extensions you need to "switch" (activate) the Enh.PAck => actually: no way back possible ! (SAP has announced that they are planing to change this behaviour; I did not follow this discussion; I believe actually there is no way back and personally I believe this (to go back) does not make sense in EHS environment)
c.) OPS_EHS_CI_1 is the Business function in Enh. pack 3
d.) LOG_EHS_CI_2 is the Business function in Enh. pack 5 (now available to all customers).
Therefore to my understanding this is the SAP approach: 1.) first activate EA-Appl, then OPS_CHS_CI_1 and then if suitable/necessary LOG_EHS_CI_2
What are the pros and cons of activation?
a.) in principal you are dealing with a "release" change (testing required; analysing new customizing activities etc. etc.)
b.) to our experince there are in most cases "strange" effects at other places; therefore you need take care regarding the activation (example: we lost some EHS functions (which are part of the former release) in release change to ECC 6.0; these functions (yes they still exists but..) are only ! part of EHS after ! an "activation" of Enh. Pack 3)
c.) at the end you get all enlargements which are part of Enh. Pack (without a choice!
In most cases the benefit is higher compared to the "technical" risks of the activation (on long term approach).
Details of the functionality of OPS_EHS_CI_1 and/or LOG_EHS_CI_2 (what are the changes etc.) are explained on high level in help.sap.com and on detailed level on SAP marketplace; therefore I will not enumerate them.
On SAP Marketplace you find a number of OSS hints "how to use Enh.Pack" / "How to activate" / Master Insturctions (Set up etc.) etc.
Personally my impression is: both Enh.PAcks (3 + 5) contain usefullnew functions which could give benefit on mid and long term in using EHS.
Keep in mind the SAP strategy: new functions (PS: Enh. Pack 6 will get in Ramp Up this year (to my recent knowledge) and will contains further EHS extensions) will always be part of enh. pack. Only if the function is needed because of legal change a new function is delivered as SP (no activation necessary).
With best regards
C.B.
Edited by: Christoph Bergemann on Apr 9, 2011 8:31 AM
Edited by: Christoph Bergemann on Apr 9, 2011 8:36 AM
Edited by: Christoph Bergemann on Apr 9, 2011 8:37 AM
Edited by: Christoph Bergemann on Apr 9, 2011 8:37 AM
Edited by: Christoph Bergemann on Apr 9, 2011 8:39 AM

Standard Field for Fiscal Period/Year

Hi
Is there any standard table field for Fiscal Period/Year so that i can use it to type my select-option field in the selection screen.
Thanks and Regards,
Navaneeth

Hi,
Check field BKPF-GJAHR and BKPF-MONAT .
And/or BSEG-ABPER ( period ).
Erwan
Message was edited by:
Erwan LE BRUN

How to have address as standard field for contacts...

Hi all, I can't find where I can add the fields for address permanently to the contact cards. Every time I enter a new contact, I have to do an >add details>address. When I click on settings in the contact's menu, only the options which contacts are show (phone, sim-card or ...) are offered. Where are the settings for the contact card? Thanks

you will have to do it manually every time...whats your phone model?? because if am not wrong, the option you want is only found in series s40 phones...
Nokia C5 -- software version 32.010
Nokia 5310

Key fields are not visible in output condition table

Hi,
     I have created few conndition tables using V/61. But i can not see Key field. It is not displaying. But when I check thru VK11 i can see that all fields are marked as key fields. example of table B018.
My problem is that , i want to make few filed non key fields rest of fileds as key fields so that there should not be any duplicate ntry based on key fields. also I do not want to maintain these two fields for each record.
Is there any exit to modify and view thesefields? or it is a security issue...bold
Your earliest response is highly appreciated.\
Thanks,
AKS

Hi Raga,
Please check the documentation under the customizing path:
IMG -> Sales and Distribution -> System Modifications ->
Create New Fields (Using Condition Technique) ->
New Fields For Pricing
Then click on the paper icon
Here is explained how to setup additional fields for pricing,
not present in the standard.
Notice the following rules:
1. the new fields must have name beginning with 'ZZ' or 'YY' in order
   to avoid problem after upgrade
2. add the new field in the table T681F for the application 'V' and the
   usage 'A'
3. these new fields must be appened to the structures KOMKAZ or KOMPAZ
   (depending they are header or item fields)
4. you should provide these fields by implementing the userexits
   USEREXIT_PRICING_PREPARE_TKOMK (header fields)
   USEREXIT_PRICING_PREPARE_TKOMP (item fields)
   in program MV45AFZZ for sales order, RV60AFZZ for invoice.
In that documentation there are some examples too.
Please check it.
Regards,
Alex

Vendor field not updated in CRM pricing condition table

Hi,
We have maintained condition table with Material and Vendor fields in ECC and table is active
After replicating this table from ECC to CRM, vendor field not updated in table and it is inactive.
There is any mapping settings required to update vendor field in CRM table from ECC.
Please help me out to solve this issue
Regards
kishore kumar

hi, the data field of vendor is a standard one or custimizing one?
I remeber there is a data mapping setting in CRM, for condition field. If you want to mapping a ERP standard field to a CRM custmizing one, you need to setting your rule in it. Maybe you can find it in SM30 view.
I can't login a CRM system now, so sorry for not offer your the view name.

Addition of field to field catalog in order to create condition table

hi,
I need to add field to SAP 5.0 Field Catalog to allow for creation of custom Condition Table. A field named Serial no. profile exists in SAP 4.6c. The equivalent should be added or created in the SAP 5.0 Field Catalog.
How do i do this. Plz help.

Thank you. i've got the solution

Fields in Field Catalog not available when creating condition table

I see that field HIEBO01 to HIEBO12 are available in Field Catalog, but I don't see these fields when creating condition table
Please let me know what I am missing here.
Any insight on this would be really helpful. Thanks guys!

you need to get them added to the pricing structure KOMKAZ or KOMPAZ based on whether you need @ header level or @ item level respectively.
and then add the logic in the sales order user exit for these added field in the pricing_prepare_TKOMK or pricing_prepare_TKOMP...again based on header level or item level.....
Then go back to the field catalog and select from the respective structure and add them, Then you can see them when creating cond tables.
Hope this helps. Hope i havent misunderstood your query.,
Regards
Sai

Project Server 2010 - create a custom enterprise project field for persons (no text, no lookup table...)

I want to create a custom enterprise project field and would like to use instead of for example a text attribute or a look-up table a field for employees (e.g. project manager) which are coming e.g. from the Active Directory. But when creating this custom
project field I cannot see such an option. What solution do you suggest as I want to avoid that everybody uses different names and spellings for e.g. the project manager and without having to fill the lookup table with all resources of the company.
Thank you so much for your help!

Hi,
Are you using Proejct Server 2007, 2010, 2013?
In case you're working with 2010 version, here is an excellent
blog about how to insert a resource picker in a PDP (project detail page).
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Create Lookup[Taxonomy] field for same taxonomy in two main tables

In MDM 7.1 SP03,
1) We have two main tables MTable1 and MTable2 in repository
2) One Taxonomy table Taxo1
3) In MTable1, Created a Lookup[Taxonomy] field for Taxo1 table
4) In MTable2, not able to create Lookup[Taxonomy] field for Taxo1
table.
Why is it not allowed to use Lookup[Taxonomy] in multiple main tables?
Thanks,
Rajesh
Edited by: Rajesh Penagalapati on Nov 12, 2009 4:53 AM
Edited by: Rajesh Penagalapati on Nov 12, 2009 4:54 AM

Hi,
Thats a limitation .Multiple Main tables cannnot share the same Taxonomy table.
You can refer the features of MDM 7.1 at
http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
Regards
Nisha

Adding quantity field for the same material number in Table control

Hello Experts,
I have an requirement, where I need to add the quantity field when the material number is repeated in a table control.
Here I show the pop-up message "Material already exists, do you want to add the quantity". If the user clicks on Yes I need to add the quantity.
I created the pop-up message using the FM " POPUP_TO_CONFIRM" and tried to add the quantity filed using COLLECT statement but I couldn't because my non-numeric field value will be different and it will insert new entry with same material in my internal table.
I have a z data base table & internal table with the below fields in it.
Best Regards,
Mani

hi deepthi,
chk a sample one which will help u. f4 hlp in table control
* Screen flow logic........
PROCESS BEFORE OUTPUT.
*MODULE PBO_MODULE.
PROCESS AFTER INPUT.
*MODULE PAI_MODULE.
PROCESS ON VALUE-REQUEST. "F4
FIELD EKPO-EBELP MODULE help_ekpo.
* populate screen field from within PROCESS ON VALUE-REQUEST(F4) call
*& Module help_responsibility INPUT
* text
MODULE help_ekpo INPUT.
**Transport values to table dynpro/screen table control
DATA: l_stepl LIKE sy-stepl,
 l_indx LIKE sy-stepl.
DATA: dynpfields LIKE dynpread OCCURS 5 WITH HEADER LINE.
* Adjust for scroling within table control
CALL FUNCTION 'DYNP_GET_STEPL'
 IMPORTING
 povstepl = l_stepl
 EXCEPTIONS
 stepl_not_found = 0
 OTHERS = 0.
l_indx = tc_ekpotable-top_line + l_stepl - 1.
 "tc_ekpotable should already have been declared
REFRESH dynpfields.
CLEAR dynpfields.
dynpfields-fieldname = 'EKPO-EBELN'.
dynpfields-fieldvalue = '00010' "wa_ekpo-ebeln.
dynpfields-stepl = l_stepl.
APPEND dynpfields.
dynpfields-fieldname = 'EKPO-EBELP'.
dynpfields-fieldvalue = '00020' "wa_ekpo-ebelp.
dynpfields-stepl = l_stepl.
APPEND dynpfields.
CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = 'SAPLZZ_EKKO' "Program name
 dynumb = '0100' "Screen number
 TABLES
 dynpfields = dynpfields
 EXCEPTIONS
 OTHERS = 0.
ENDMODULE. " help_ekpo INPUT
rgds
Anver
if hlped kindly mark points

Need to add new fields to the condition table

Hello All,
The requirement is to create the new condtion table for MM containing the following fields and maintain the entries in this table:
- client
- characteristic
- class
- internal characteristic.
THe condition tables are created via tcode M/03 or through the customizing path
Material Management > Purchasing > Conditions > Define Price Determination Process > Maintain Condition Table.
The problem which i am facing is as follows :
-SAP has the standard procedure for the generation of the condition tables . Selected fields are made available by SAP in the field catalog and we can select only from the those available fields. Once we select the required fields the condition table is automatically generated in the background.
-As the requirement is, we need to have 4 fields in the generated condition table (client, characteristic, class and internal characteristic), but the problem is that none of these fields are available in the field catalog which is provided by SAP (in tcode M/03, M/04 and M/05).
-Designing of the Z table wonu2019t be useful as we would not be able to use the Z table as the condition table.
Can you please suggest how can we add the desired field to the existing field catalog in M/03 or is there any other alternate solution to this ?
Thanks in advance for your help.

>
Rinkesh Doshi wrote:
> Hello,
>
> The specific ABAP question which I have is :
>
> Is there any way in which we can enhance the existing field catalog in M/03 tcode to include the 4 new fields (client ,characteristic,class,internal characteristic) ?
>
> Thanks.
Please post your code which you developped until now and show us where the problem is. I cant see any ABAP related question.

TD Shipment ouput - New filed in condition table

Hello,
We are using TD Shipment functionality. We have an output type defined under "Bulk transportation scheduling". FOr this output currently we have an access sequence which has only one table with key field as "Transportation Planning Point".
Now we need to add another table to this at higher level with key combination of "Transportation Planning Point and Issuing Plant (PSWRK). But after adding this table to the sequence we are not able to use it, as we are facing following problems:
1. Initially the field assignment was not happening so wehave defined PSWRK in the structure KOMBOI. Now the assignment is happening.
2. But when we update the shipment, the output does not get triggered. The output analysis shows that access is not made. The system is not able to fetch the value for PSWRK.
-Is it because the ouput is at header level and we have used a field that is defined at item level?
- How can we use the item level field for this output? Do we need to define it anywhere else to be picked up?
Any pointers are appreciated.
Best Regards,
Amit

Hello AMit,
If you want to use a new field for the setup of a condition table, it
has also to be defined in the structure KOMKBV7 (included in KOMB)..
In addition, you will need to make use of user exits to populate these
fields in the communication structures.
In routine LVCOMFZ1 the following User-Exits are available:
- USEREXIT_KOMPBV7_FILL (Shimpent fields for Header and Stage)
- USEREXIT_KOMPBV7_PARTNER (Shipment fields for Partner)
good luck
david

SDIMA: Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ

Hi Experts,
when checking condition records consistency between CRM and ERP via transacation SDIMA we get the following error for one of the conditon records: 'Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ'. Can anybody explain to me where this message could come from? To my understanding field 'SUPP_EXIST' only exists in CRM condition tables for technical reason. So no way to compare this against an ERP condition table field, is there?
And related to this: I found that this error message is triggered from method CL_CND_DIMA_CRM->COMPARE_MBDOC. As the DIMA-Compare is triggered asynchronously and just setting a break-point is no option therefore, I was wondering if anybody knows a way of debugging this method in order to find out what the coding does in detail before the message is thrown.
Thanks a lot for your help!
Cheers,
Jens

Hi Brian and the other Experts,
thanks for your help. Unfortunately, I don't have a single record with this problem but a lot more. So it is not possible to correct this manually. Also, I would not know how to correct this anyhow as I don't understand what field in R/3 should map to field SUPP_EXIST in CRM condition tables. Let me explain:
From my understanding, in CRM (leave aside scales) we have two database tables for each condition table, a central and a supplemental table. A condition record always creates a data record in the central table and nothing is inserted in the supplemental table in case that the fields form the supplemental table are not needed. However, when there are less common condition features involved (e.g. uppler limits), then an additional data record will be created in the supplemental table with the relevant data. And this is when field SUPP_EXIST comes into play as it is an indicator for the system that a data record exists for that condition record also in the supplemental table.
The condition record data model in R/3 is completely different. For CRM condition table CNCCRMPRCUS801 the following tables in R/3 are involved: A801, KONH and KONP. And there is a data record for each of them for a given condition record. There is no concept of having a supplemental table as far as I understand it so where exactly would I find this SUPP_EXIST in R/3 so that I can make sure it does not deviate from the data in CRM?
Would be great if someone could give me another hint. What am I getting wrong?
Cheers,
Jens

Standard field for Country of Despatch in condition table

Similar Messages

Maybe you are looking for