FM for creating Condition Records

Is there FM for creating Condition Records for output type like transaction VV11 (Create Output - Condition Records: Sales)

Hi there,
FM for condition records? Why do you want to think of a FM for creating conditon records?
Condition records is a master data that has to be manually created as per the business requirement.
But what we can do is that if the data ia existing in an external legacy system, we can migrate that into SAP through a BAPI / BDC or LSMW depending on the volume of data.
But in other cases condition records are manually created in SAP system.
If at all you have a function module to create condition records, how would you ensure that it feeds correct data into the condition records? What key combination would the system take & what data would you want the FM to upload?
How will you monitor what data is uploaded,.
Regards,
Sivanand

Similar Messages

Function Module for creating condition record (XKOMV table record)

Hi,
I have a requirement as like below,
In the repair order i need to sum the GRWR condition type's conditional values for all the line items (Except deliverable line item) and then i need to create an condition type GRWR under the deliverable line item with the above calculated conditional values,
the table XKOMV will be having details about all the line item's condition types, in this table i need to add one more new record with the condition type of GRWR and the above calculated conditional values under the deliverable line item.
for the above logic i am using the user exit
USEREXIT_SAVE_DOCUMENT_PREPARE
All the above things need to be done when the user click the save button in the transaction (VA01/VA02).
Problem here is table XKOMV contains somany fields so manually we can't create xkomv record, is there any Function module to create condition type record?
Regards,
Manikumar
Edited by: Manikumar Shanmugam on Mar 8, 2008 3:53 PM

Hi,
You can use Function module PRICING_CHECK to check condition record. Do a where-used list on it to see how to call it.
Regards
Kiran Sure

Error while creating condition record

Hi
Am using 4.7 and creating condition record while saving condition record am getting error NO UPDATE SERVER FOUND FOR CONTEXT E, So am stuck up and do not know whom to contact is it error for BASIS? or related with SD kindly help.
Thanx

Hi Mukesh
As you are getting error NO UPDATE SERVER FOUND FOR CONTEXT E, while saving the condition record, kindly consult your BASIS consultants and ask them to check wheather the pricing related tables and structures have been copied and uploaded properly or not.
Regards
Srinath

Creating condition records in product

hi,
I am trying to create condition records for a product.For a sales order (TA) i create, the pricing procedure determined is RVCXUS. But i dont see any of the condition type which matches condition type for a product (in F4) and condition type maintained in RVCXUS.
Please let me know where from the condition type(in F4) comes in a product. It will not include all condition type we see in spro?
Regards,
Rahul

Hi Rahul,
To see a particular codition type in F4 help, you need to assign your "condition type/(s) in pricing procedure" to condition group being used for your application area. try following:
1. check condition group being used to the application SAP CRM in SPRO > Customer Relationship Management> Master Data> Products> Special Settings for Sales Operations--> Assign Condition Group to Application CRM
2.Assign the condition types in your pricing procedure to the above condition group by choosing SPRO>Customer Relationship Management> Master Data --> Conditions and Condition Technique --> Condition Technique: Basics Create Maintenance Group
Let me know if this works....!!
Best Regards,
VIshant Jain

Report for freight condition records

Dear Freinds
In my transportation module project, requirement is report for freight condition records.
We have been created two tables in one access sequence, two tables are: 1. route/ship-to-party 2. route
They maintained more condition records. They want to see all vondition records in one single report.
Report based on those two tables. But those two tables are storing in KOMG Structure.
But price is storing in KONP table. How to fetch both in to repor.
With regards
Lakki

Let us say the condition tables are 001 and 002
Now you need to go to database tables A001 and A002 in SE16
Give the name of your condition type for which you want to get all the condition records
Execute now.
Now you will get all the condition records for the condition type created for the table say A001
Hope this solves your problem. You can reward if this helps.

Transaction used for maintaining condition record for contract

Hi All,
In one of the issue user is not able to print contract,we have noticed that default printer is set for user.I need to check what condition record is maintained for user.
Can anyone let me know what is the transaction used for maintaining condition record for contract output.
Regards,
Dharmesh

Hi
MN01 Create Message: RFQ
MN04 Create Message: PO
MN07 Create Message: Outline Agreement
MN10 Create Message: Schd. Agmt. Schedul
MN13 Create Message: Service Entry Sheet
MN21 Create Condition: Inventory Mgmt
MN24 Create Message: Shipping Notif.
MN27 Create message: rough goods receipt
MN10 / MN11 - Scheduling Agreement Delivery Schedule
Vijay

Creating condition record by uploading

Hello all,
I am using FM BAPI_PRICES_CONDITIONS to create condition record.
But its creating the record even if i gave the invalid details ( like invalid material number,...).
Can you please tell me how can i handle the errors using this FM.
Thanks in advance.
regards,
Lokesh

hi..
This code snippet inserts a condition record for Pricing condition type Z123 with key sales order
and line number.
CONSTANTS: lc_kschl_z123 TYPE kscha VALUE 'Z123'.
DATA: lv_datum TYPE sydatum,
lv_count TYPE kopos,
lv_unit TYPE kpein,
is_bapicondct TYPE bapicondct,
is_bapicondhd TYPE bapicondhd,
is_bapicondit TYPE bapicondit,
it_bapicondct TYPE STANDARD TABLE OF bapicondct,
it_bapicondhd TYPE STANDARD TABLE OF bapicondhd,
it_bapicondit TYPE STANDARD TABLE OF bapicondit,
it_bapicondqs TYPE STANDARD TABLE OF bapicondqs,
it_bapicondvs TYPE STANDARD TABLE OF bapicondvs,
it_bapiret2 TYPE STANDARD TABLE OF bapiret2,
is_bapiret2 TYPE bapiret2,
it_bapiknumhs TYPE STANDARD TABLE OF bapiknumhs,
it_mem_initial TYPE STANDARD TABLE OF cnd_mem_initial.
lv_datum = sy-datum.
lv_count = 1.
LOOP AT gt_vbap INTO wa_vbap.
* BAPI Structure for Condition Tables
is_bapicondct-operation = '009'.
is_bapicondct-table_no = '700'.
is_bapicondct-applicatio = 'V'.
is_bapicondct-cond_usage = 'A'.
is_bapicondct-cond_type = lc_kschl_z123.
"Set the varkey from A700 table key fields
CONCATENATE wa_vbap-vbeln wa_vbap-posnr
INTO is_bapicondct-varkey.
is_bapicondct-valid_to = '12/31/2009'.
is_bapicondct-valid_from = lv_datum.
is_bapicondct-cond_no = '$000000001'.
**** BAPI Structure of KONH with English Field Names
is_bapicondhd-operation = '009'.
is_bapicondhd-cond_no = '$000000001'.
is_bapicondhd-created_by = sy-uname.
is_bapicondhd-creat_date = sy-datum.
is_bapicondhd-cond_usage = 'A'.
is_bapicondhd-table_no = '700'.
is_bapicondhd-applicatio = 'V'.
is_bapicondhd-cond_type = lc_kschl_z123.
is_bapicondhd-varkey = is_bapicondct-varkey.
is_bapicondhd-valid_to = '12/31/2009'.
is_bapicondhd-valid_from = lv_datum.
*** BAPI Structure of KONP with English Field Names
CLEAR is_bapicondit.
is_bapicondit-operation = '009'.
is_bapicondit-cond_no = '$000000001'.
is_bapicondit-cond_count = lv_count.
is_bapicondit-applicatio = 'V'.
is_bapicondit-cond_type = lc_kschl_z123.
is_bapicondit-scaletype = 'A'.
is_bapicondit-scalebasin = 'B'.
ADD 1 TO is_bapicondit-scale_qty.
is_bapicondit-calctypcon = 'B'.
lv_unit = wa_vbap-kwmeng.
is_bapicondit-cond_p_unt = lv_unit.
is_bapicondit-cond_value = wa_vbap-value.
is_bapicondit-condcurr = wa_vbap-waerk.
APPEND: is_bapicondct TO it_bapicondct,
is_bapicondhd TO it_bapicondhd,
is_bapicondit TO it_bapicondit.
ENDLOOP.
*** BAPI for pricing Condition Records
CALL FUNCTION 'BAPI_PRICES_CONDITIONS'
TABLES
ti_bapicondct = it_bapicondct
ti_bapicondhd = it_bapicondhd
ti_bapicondit = it_bapicondit
ti_bapicondqs = it_bapicondqs
ti_bapicondvs = it_bapicondvs
to_bapiret2 = it_bapiret2
to_bapiknumhs = it_bapiknumhs
to_mem_initial = it_mem_initial
EXCEPTIONS
update_error = 1
OTHERS = 2.
IF sy-subrc EQ 0.
WRITE: /1 'Return Messages for Condition create'(t03).
LOOP AT it_bapiret2 INTO is_bapiret2.
WRITE: /1 is_bapiret2-message.
ENDLOOP.
ULINE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'
IMPORTING
return = is_bapiret2.
ENDIF.

. Is it possible to create condition record in both CRM as well as in R/3

hi,
. Is it possible to create condition record in both CRM as well as in R/3? Explain in more details.
Regards,
babu

Hi Babu,
No. You cannot create condition records in CRM when back end is R/3.
Condition records should be created in R/3 and replicated to CRM.
You cannot extend condition records in CRM.
Reward the Points.
Thanks,
Srini.

T code for maintaing condition record in MM pricing

Hiii ..MM GURUS...
Can anyone let me know the transaction code for maintaing condition records for condition types in MM pricing .
Regards
SARFRAZ..

MEK1 with appropritate key combination

Create condition record with reference to existing condition record

how to create condition record with reference to existing condition record?

Hi,
See this link :
http://help.sap.com/saphelp_47x200/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm
You can create with reference with Tcode : VK14 (or VK34)
Or in VK12, you can copy condition records with copy rules.
Regards,
Lionel

Is their any function module for deleting condition record i am trying

Hi Experts,
Is their any function module for deleting condition record i am trying this way.......
DATA: TABLE (4) TYPE C.
DATA: KNUM LIKE KONH-KNUMH
DATA: K_VEWE LIKE T681-KVEWE VALUE 'A'.
DATA: T681_STR LIKE T681.
DATA: LV_NUM TYPE I.
GET PARAMETERS
PARAMETERS: TABNO LIKE T681-KOTABNR.
PARAMETERS: TESTMODE DEFAULT 'X' AS CHECKBOX.
REFRESH INT_KNUMH.
Select single * from T681 into T681_STR
where kvewe = K_VEWE AND
KOTABNR = TABNO.
IF SY-SUBRC NE 0.
WRITE: / 'No entry in T681 for number ', TABNO.
WRITE: / 'Check whether corresponding condition table exists.'.
EXIT.
ENDIF.
TABLE = T681_STR-KOTAB.
SELECT KNUMH FROM (TABLE) INTO KNUM.
SELECT SINGLE * FROM KONH WHERE KNUMH = KNUM.
IF SY-SUBRC NE 0.
INT_KNUMH-KNUMH = KNUM.
COLLECT INT_KNUMH.
ENDIF.
ENDSELECT.
DESCRIBE TABLE INT_KNUMH LINES LV_NUM.
IF LV_NUM EQ 0.
WRITE: / 'No inconsistent entries found.'.
WRITE: / 'Each record in the condition table has a corresponding.'.
WRITE: / 'entry in the KONH table.'.
EXIT.
ENDIF.
LOOP AT INT_KNUMH.
IF TESTMODE IS INITIAL.
DELETE FROM (TABLE) WHERE
KNUMH = INT_KNUMH-KNUMH.
IF SY-SUBRC = 0.
WRITE: / 'KNUMH =', INT_KNUMH-KNUMH(10), ' deleted from table ' ,TABLE.
ELSE.
WRITE: / 'DELETE: SY-SUBRC is', SY-SUBRC , ' FOR KNUMH = ' .
WRITE: INT_KNUMH-KNUMH(10).
ENDIF.
ELSE.
WRITE: / 'TESTRUN: KNUMH =', INT_KNUMH-KNUMH(10).
ENDIF.
ENDLOOP.
is their any Standerd Function module for comparing tables if the condition record not exist in it has to exit if it is their then compare those two tables if not exist in one table also that has to be delete the condition record
Please let me know .....

Hi,
You can use Function module PRICING_CHECK to check condition record. Do a where-used list on it to see how to call it.
Regards
Kiran Sure

BAPI or FM to Create Condition Records (VK11)

Hi!
Is there a BAPI or a FM (or something else) to create condition records in the same way as with transaction VK11 (or XK15)?
I am aware of the LSMW program RV14BTCI (althought never have used it).
Thanks!
Kind regards,
Igor

Hello Igor,
It's not trivial, but let's have a try. Use transaction SALE to get into the ALE business. Then option Modeling and implementing Business Processes -> Maintain distribution model.
Get into change mode and create model view (any name will do). Then selected the newly created node and Add message type. Here you have to enter the sending and receving system and the message type (COND_A).
Afterwards select the node and then via menu Environment->Generate partner profiles execute the partner profile will be generated automatically.
Now you are able to send a condition records from system A to B.
Regards,
John.

Postings in SAP HR for creating delta records for Time Management

Hi Experts,
I am trying to test delta load for SAP HR Time Management Datasources. I am fairly new to SAP HR and need some help.
Where do we create postings in SAP HR for creating delta records which can be imported to BW. This is for the data sources 0HR_PT_1 and 0HR_PT_2.
Any help is appreciated. Will assign full points
Regards
Sunil Kumar.

Hi,
In order to test the above data sources you need to have some employee enter his time details or change the entered time details. That will create some delta records for the planned or actual times. CAT2 transaction should help entering the time details in SAP.
Hope it helps.

If std iview can b used for creating qualified record

Hi all
standard iView can b used for creating qualified record ? if possible and how it is? please let me know ASAP
Regards
Sunil

Hi Sunil,
Yes it is possible to create qualified record using Standard MDM iViews.
Please follow the steps mentioned below:
1. Create the Item Details iView with Create and Edit option enabled and select the Qualified table fields along with the other fields.
2. Go to the option Relationship and Qualified Display fields. You will find the entry of the Qualified field that you have selected earlier.
3. Edit the entry and select the Qualifiers that you want to appear in the output. Also select the Non-Qualifier as well.
4. Save the iView and preview it.
Note: To create an entry in the Qualified table first create the main table record and click on save. Then click on Edit to make an entry in the Qualified tables.
Regards,
Jitesh Talreja

Make Condition exclusion type to be active for different condition records

Hi
We are currently using three condition types in the pricing procedure.
Say for eg. YWBP- F Charges, YADJ -C charges and YHDG-Handling fee
We have set condition exclusion for the combination of YWBP and YHDG and
YADJ and YHDG.
YHDG condition type has two condition records.. say for eg. 512 and 596.
The materials defined for 512 condition records is YAU and YAX and for 596 is YAV.
Now my question is that whenever condition types YADJ gets picked up fo YAU, YAX and YAV then condition type YHDG shouldnot get picked up. (The above condition exclusion group will perfectly caters to this requirement.) but now the cache is the business has a requirement that
When ever condition type YWBP gets picked up for the material 'YAV', then the condition type 'YHDG' (with 596 table condition records) should also get pick up in the sales order.
Is there any way to achieve this with current settings of condition exclusion indicator.
Thanks in advance.

Hello Vicky
Not knowing the relationship between ZCPD and ZDUT, it is hard to answer your question. I am not sure how ZDUT is affected by ZCPD.
By your description, there is a requirement in the pricing procedure that is setting the exclusion indicator to X for ZCPD under certain conditions. May be that is not a right solution for your situation.
I would suggest using condition exclusion groups and then assigning condition exclusion group to the pricing procedure to meet your requirement. Let ZCPD be in group 1, all other conditions that you want excluded when ZCPD is present ( but not ZDUT) in group 2. Then use the exclusive option while assigning to the pricing procedure.
All these config steps can be found here:
SPRO/IMG/Sales and Distribution/Basic Functions/Pricing/Condition Exclusion/Condition Exclusion For Groups Of Conditions
Link: http://help.sap.com/erp2005_ehp_04/helpdata/EN/93/7432eb546011d1a7020000e829fd11/frameset.htm
Hope this helps.

FM for creating Condition Records

Similar Messages

Maybe you are looking for