This website is not affiliated with, sponsored by, or approved by SAP AG.
Logistics : MM and its sub-modules (WM, IM, PO, LIS)
6 posts • Page 1 of 1
I wanted to create to access sequence based on PO document type. Since document type is not included in field catalog on condition table, i need to extend additional field catalog PO doc. type (BSART).
I go to IMG->MM->Purchasing->Condition->Define price determination process->Extend field catalog for condition tables. When i add field BSART, after clicking enter, warning message pop up:
Choose the key from the allowed namespace
Message no. SV019
You have attempted to create an entry and have used a key which is not in your namespace.
This can cause problems in later upgrades because the entry could be overwritten by an import, or overwrite an existing entry.
Check your entry and try to enter a key value from your namespace.
You can display the namespace definition with RDDKOR54.
If you must use the key entered, document your change so that it can be repeated after an upgrade or release change if necessary. If you put the data in a change request, you can export it before an upgrade or release change, and import it again afterwards.
I ignore the message, save. However, when i create new table, field BSART was not show up. On the contrary, when i checked to the previous transaction, field BSART already showed up.
Any hints pertaining this issue?
Looking forward for help.....
To use your own fields for the price determination process, you must extend the communication structure table (KOMK, KOMP or KOMG where the KOMG Table represents the sum of KOMK and KOMP and contains all the fields that can be used in price determination). New fields entered in KOMK and/or KOMP are adopted in the structure KOMG automatically. There have been two enhancements that you should look at when you would like to append KOMK or KOMP as detailed hereunder -
1) In respect of KOMK - Use Function Module EXIT_SAPLMEKO_001 (User Exit LMEKO001) which includes ZXM06U14.
2) In respect of KOMP - Use Function Module EXIT_SAPLMEKO_002 (User Exit LMEKO002) which includes ZXM06U15.
Which particular steps would you like to know in more details?. The fact is that you will have to get your ABAPer to activate the related user exit (that I have mentioned) if you wish to extend field catalog for your pricing-related communication structure KOMK or KOMP. Once these fields are extended, you can simply follow the standard configuration steps to add them to your condition table.
hi i am also trying to add the same field(PO document type) field)
i tried the above steps and was able to add the ZBSART field in "Extend Field Catalog for Condition Tables",
next i created a new condition table with ZBSART and then maintain it under access sequences.
i also maintained the condition using MEK1 tcode. while in MEK1, i noticed that when i press the F4 in the order type field, nothing was shown, by right it should be listing all the available PO doc type..hmm....
next, when PO was created, the condition was not being called.
and i saw the below msg in analysis
Description:Access not made (initialized field)
anyone got any idea?
6 posts • Page 1 of 1
Who is online
Users browsing this forum: Google Adsense [Bot] and 4 guests