BAPI_PO_CREATE1 -- Condition Record filling

Hi,
In this BAPI how to insert the Condition records to be filled ...
    CALL FUNCTION 'BAPI_PO_CREATE1'
         EXPORTING
              POHEADER         = G_BAPIMEPOHEADER
              POHEADERX        = G_BAPIMEPOHEADERX
         IMPORTING
              EXPPURCHASEORDER = G_EBELN
              EXPHEADER        = GSTEST
         TABLES
              RETURN           = G_BAPIRET2
              POITEM           = G_BAPIMEPOITEM
              POITEMX          = G_POITEMX
              POSCHEDULE       = G_BAPIMEPOSCHEDULE
              POSCHEDULEX      = G_POSCHEDULEX
              POCOND           = G_BAPIMEPOCOND
              POCONDX          = G_BAPIMEPOCONDX.
what are the mandatory fields,..
Any helpful inputs on this will be rewarded points
Rgs
Lakshmiraj.A

Pls help,
Any useful inputs on this will be rewarded points.

Similar Messages

BAPI_PO_CREATE1 condition type are creating duplicate records

Hello Experts,
Currently I am creating Purchase orders using BAPI_PO_CREATE1 . When I am passing Condition related records to the same BAPI , second line item onwards , it creates multiple records of same condition type .
I have also looked into threads in SDN for the same , and they have suggested to create PO using BAPI_PO_CREATE and later use BAPI_PO_CHANGE to pass condition records. I have tried the same , but still second line item onwards it creates multiple records. Please tell me how do I resolve this issue.
Thanks
Trishna

Hello All,
This duplicate condition record creation may happen due to a setting in the MM configuration, where the system tries to pull in the history condition records ,based on the same set of condition record determination parameters.
Please contact the MM functional consultant in your team for settings change in detrmination of condition records under " MM-Purchasing " section.
Best Regards,
Kumaar.S

BAPI for creation of condition records MEK1 tcode

Hi,
Any one used to upload condition records data for MEK1 transaction code. Please give me reply any once knows.
Thanks in advance
Shaik Basha

Hi Vijay,
Thanks for giving reply. I checked BAPI_PO_Change and
BAPI_PO_CREATE1. But in these two PO number is the mandatory field. In mek1 tcode, for particular condtion type key combination i dont have any PO field that time i will use this FMs. Please give me advice regarding this.
I am also facing some other problem i.e to change the routing master data. I alreay downloded data from routing master in excel and i did changes in excel. Now i';ll upload the excel to sap that will update the routing master. If u have any idea for updating the routing master data.please send me the fm.
Regards
Shaik Basha.

Output device for output condition record

How can i make an output device a required entry when creating a new output conditon record?
Example: When going into VV31 and setting up new output condition record, I am trying to force user to specify an output device.
Can some one let me know if it is possible to do?
Thank you.

Hi
Write a Field Exit for that field
and trigger a error when it is not filled , such that the user always enters it.
Reward points if useful
Regards
Anji

Pricing condition record

Hi All,
There is a problem with the invoice condition records.In our case invoices are actually created via Idocs.
Usually the condition record type is sent in the Idoc and the corresponding condn. type comes in the invoice.But in one case,the Idocs do not have a particular condition record type present in the data segment ,yet the invoice when created has the condition type in it.
Does any one have a idea if the condition type gets picked from any master table or is there any other way it appears in the invoice.
As far as the program that creates the Idocs,It picks the condition records from a Z table and fills in the Idocs.
Thanks for your help!
Regards,
Gowthami SK

Hi Sam,
the preceding document is the sales order.
the scenario is like the sales order gets created through Idocs (msg type:VLCCPO),the pricing condition record is filled in the Idoc ( KSCHL) and it appears in the invoice.
But in a particular case,there is no condition type in the Idoc ,yet the condition type appears in the invoice.
Is it possible that any standard pricing condition has been defined???
Regards,
Gowthami SK.

Mass Upload of condition records in APO system.

Hi All,
I wanted to mass upload condition records in to the APO system for the transaction /N/SAPCND/AO11 from an external file.
Is there any FM available?
If FM is not available...which one is the best way to do this?
LSMW?? or BDC???
Please guide me..
Thanks,
Babu Kilari

At least the key fields of the conditiontable
(here 800) must be filled in structure ls_komg.
ls_komg-vbeln = '1234567890'. " document number
ls_komg-posnr = '000010'.      " item number
clear wt_komv.
ls_komv-kappl = 'V '.        " Application V = Sales
ls_komv-kschl = lc_kschl.    " Condition type
ls_komv-waers = 'EUR'.       " Currency
ls_komv-kmein = 'ST'.        " Unit of measurement
ls_komv-kpein = '1'.
ls_komv-krech = 'M'.         " calculation type;
                              "M = Quantity - monthy price
ls_komv-kbetr = '1234.56'.   " new condition value
append ls_komv to lt_komv.
call function 'RV_CONDITION_COPY'
exporting
    application              = 'V'
    condition_table          = '800'      " cond. table
    condition_type           = lc_kschl   " cond. type
    date_from                = '20061101' " valid on
    date_to                  = '20061130' " valid to
    enqueue                  = 'X'        " lock entry
    i_komk                   = ls_komk
    i_komp                   = ls_komp
    key_fields               = ls_komg    " key fields
    maintain_mode            = 'A'        " A= create
                                          " B= change,
                                          " C= display
                                          " D= create
with reference
    no_authority_check       = 'X'
    keep_old_records         = 'X'
    overlap_confirmed        = 'X'
    no_db_update             = space
importing
    e_komk                   = ls_komk
    e_komp                   = ls_komp
    new_record               = lv_new_record
tables
    copy_records             = lt_komv
exceptions

Condition records in idoc

hi
whenever po is created or changed idoc should get triggered, as it is done already,now the issue is the condition records also be included in idoc whenever po is created or changed.
can anyone explain me how to do that?
and what is idoc view and how it is related to condition records.

IDOC Views are used for IDoc outbound processing where you dont want to send an entire IDOC out when all you need is just some of the segments.
To improve performance when generating IDocs, you can use views to ensure that only the segments relevant to the current business process are filled with data. Views are therefore only important for IDoc outbound processing
chk the sap doc.
http://help.sap.com/saphelp_47x200/helpdata/en/d5/edf160dcdc11d1890c0000e8216438/frameset.htm
Edited by: Mahalakshmi Padmanaban on Feb 16, 2010 3:02 PM

Condition record exist, but has not been set

I am creating proforma invoice for STO replenishment delivery. I am getting error log "Billing type contains split criteria, n invoiced:123456789, invoice not required". But I am able to save it. I used all standard settings for copy control and billing type.
For the proforma invoice the condition records are picking up some times and some times not picking up. In the analysis its showing "Condition record exist, but has not been set". When I update with carry out new pricing some times its updating with condition records some times not. I need a solution urgently. Please help.
Edited by: k c on Nov 4, 2009 7:50 AM

Hello,
The message "condition record exists, but has not been set" tells you
that the condition record exists, but has not been set in the document.
If pricing was carried out again for the document item, then the
condition would be set.
This can have different causes:
The condition was deleted manually in the item condition screen.
The condition record was created later. Please note that order
processing and pricing have buffer mechanisms. This means that a newly
added condition record might only be found after order processing have
been left completely and then started again.
When an item was added, the condition record was accessed with key
fields other than change time. This could lead to different results in
the requirements check at the time of adding and the change time. This
can occur when modifications are made.
In billing (or when copying orders): Certain condition types were not
determined in the source document (this is usually controlled by the
pricing requirements). When creating the document, the document flow
(TVCPF,TVCPA) is processed using a pricing type that does not
redetermine these condition types, although they are supposed to be
called via the requirments."
Please check if any of those reasons apply to your problem.
Note that the condition type is determined just in the moment when
   the billing item is created. And it then that the userexit fills the
   field. When you save the billing document, pricing is called.
   Please ensure that you have any userexits switched off and then test
   this issue again.
If you have access to OSS notes. please see:
     24832      Pricing rules / TVC
    130416     Requirements in the condition preliminary st
      27636     Message: Condition exists (removed manually)
    859876     Condition is missing: Message VE 108 or VE 008
I hope you find this information very helpful and hopefully it will solve your problem.
Regards,
Martina McElwain
SD - Forum Moderator

Condition Record exits (but removed manually)

Dear All
when i am creating SA , some condition types are not being picked up. syastem shows Condition records exits (but removed manually) though problem doesnot fall under any of the reason given in analysis. Not to understand why is this happening
Help plzzz
Regards-
Ram

The message "condition record exists, but has not been set" indicates you that the condition record exists, but has not been set in the document. If pricing was carried out again for the document item, then the condition would be set.
There can be different causes/possibility for this, few of them can be:
The condition was deleted manually in the item condition screen.
The condition record was created later. Please note that order processing and pricing have buffer mechanisms. This means that a newly added condition record might only be found after order processing have been left completely and then started again.
When an item was added, the condition record was accessed with key fields other than change time. This could lead to different results in the requirements check at the time of adding and the change time. This can occur when modifications are made.
In billing (or when copying orders): Certain condition types were not determined in the source document (this is usually controlled by the pricing requirements). When creating the document, the document flow (TVCPF, TVCPA) is processed using a pricing type that does not redetermine these condition types, although they are supposed to be called via the requirements."
Note: that the condition type is determined just in the moment when the billing item is created. And it then that the user exit fills the field. When you save the billing document, pricing is called. Please ensure that you have any user exits switched off and then test this issue again.
Also, refer following SAP Notes
Notes 24832 Pricing rules / TVC
Notes 130416 Requirements in the condition preliminary st
Notes 27636 Message: Condition exists (removed manually)
Notes 859876 Condition is missing: Message VE 108 or VE 008
Hopefully this would assist you in your requirement.
Thanks & Regards
JP

Rebate condition record T code VBO1-Error Message

Hi,
I am getting error message while creating rebate condition record T code-VBO1-Error Msg-862 system cannot read the structure for table,because of this i could not create condition record.
(This error has occured while i am testing rebate process in IDES and it happen while creating condition record for rebate agrement,After filling the initial values in T code VBO1 and when click on enter the above mentioned error message has come).
Please give the solution to create condition record.
Thanks in Advance
Regards
Praveen P C

Hi,
You said you are trying to do this stuff in IDES right.
If you are using IDES provided by a company and where many people play on IDES, then you can get many such issues...
This is by our experience. Today you do something in IDES and tommorow that thing or config is screwed up by others.
If you have your own IDES, then check the suggestion given by the forum Guru's.
Regards,
SB

STO Problem - Condition record missing

Hi,
I am facing the following issue while creating P.O
I have mentined a pricing procedure with condition Pi01 ( for moving average price ), ZMRP ( which is maintained in SD. condition records are filled ) and ZSTO which for calculating excise and is based on ZMRP.
Condition record of ZSTO is filled in the MM side.
Now, when I try to make a P.O. by ME21, I get the error message that " mandatory Condition ZSTO is missing". I have analysed the ZSTO access sequence. It OK and maintained.
The Error Message No. is V.1801.
As a result of the above issue, the excise is not flowing in the order when doing goods transfer from Plant.
Thanks & regards,
KVinod

Hi,
My main issue is that in the P.O, which I am creating by ME21N, I am getting an error message that "Condition Type ZSTO's records are missing" . Even though its record is maintained in the correct combination. The access sequence is correct. It is assigned at the right place in STO pricing procedure.
To elaborate further on this, in my STO pricing procedure, I am using condition type P101( for moving average price), ZMRP ( which is the MRP of the item and maintained in SD by VK11), Freight condition and condition type ZSTO . ZSTO is maintained in the MM side.and is calcuIated as 4% of ZMRP. I am getting all the condition while doing ME21N, except ZSTO.
Pl give me solution, why I am not getting the ZSTO condition record in ME21N.
Thx & regards,
KVinod

Error in creation of a condition record

Hi to all, I've this error when I try to create a condition record :
Implementation of Method FIELD_CHECK/DEFAULT_VALUE_SUGGESTION for BAdI /SAPCND/ROLLNAME for filter ZIUSERSTATUS is missing
Message no. /SAPCND/MAINTENANCE719
Diagnosis
Implementation of BADI /SAPCND/ROLLNAME or method FIELD_CHECK/DEFAULT_VALUE_SUGGESTION is missing for the filter characteristic ZIUSERSTATUS.
If, however, the implementation is correct (see BADI Interface Documentation) and active, there is an error in the condition maintenance layer.
System Response
An exception or error occurred because condition maintenance cannot check, convert or lock/unlock the fields of a condition record.
Procedure
Contact the department responsible for carrying out the missing implementation in the case of application fields in the customer namespace. SAP is responsible for SAP fields which are set in the field catalog (/SAPCND/CTFC) and delivered, and if the field is supported as a possible field in a condition table. SAP is also responsible for the implementation of usage fields for SAP applications, just as with condition technique fields.
In cases where SAP is responsible, contact your responsible support organization.
Could someone help me please ?

Hi I just put the coding:
e_was_executed = 'X'.
into every method and however it worked.
Best Regards

How to Delete the condition record in CRM

HI,
Can you please help me how to delete the condition record from condition table in CRM.
Please explain the usage of FM CRMXIF_CONDITION_SEL_DELETE with examples.
I have also read the documention of the function module. How to use this FM for custom defined condition table.
(this is the code given in Documentation)
DATA-OBJECT_REPRESENTATION         = 'E'
DATA-SEL_OPT-CT_APPLICATION              = 'CRM'
DATA-SEL_OPT-OBJECT_TASK                    = 'D'
DATA-SEL_OPT-RANGE-FIELDNAME        = 'PRODUCT_ID'
DATA-SEL_OPT-RANGE-R_SIGN                  = 'I'    (Including)
DATA-SEL_OPT-RANGE-R_OPTION           = 'EQ'
DATA-SEL_OPT-RANGE-R_VALUE_LOW = 'PROD_1'
Thanks
Shankar

Hi Shankar,
I am using the same CRMXIF_CONDITION_SEL_DELETE function module to delete condition record present in CRM.
But it is giving me below error in the return table of the FM after i run the program. Can you please correct me if I am doing any thing wrong?
Error in lt_return: SMW3     CND_MAST_SEL_DEL_EXT_VALIDATE     CND_M_SD
code:
ls_range-fieldname = 'PRODUCT_ID''.
ls_range-R_SIGN = 'I'.
ls_range-R_OPTION = 'EQ'.
ls_range-R_VALUE_LOW = '123456'.
APPEND ls_range TO lt_range.
MOVE lt_range TO ls_entry-SEL_OPT-range.
ls_data-SEL_OPT-object_task = 'D'.
ls_data-SEL_OPT-ct_application = 'CRM'.
ls_data-object_representation = 'E'.
CALL FUNCTION 'CRMXIF_CONDITION_SEL_DELETE'
EXPORTING
    DATA          = ls_date
IMPORTING
   RETURN        = lt_return
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
IMPORTING
    return = lt_ret.
Edited by: Saravanaprasad Nadar on Jul 7, 2010 1:27 AM

Free goods condition records - Usage in Sales Order

HI,
I have so many condition records in various KOTN9xx tables, which are for issuing free goods. If I see a sales order item, that is a free good, how do I know, on what basis (based on which condition record, in which condition table) that free good was issued?
Technically speaking: Similar to KONV table for storing transaction data on pricing, is there a table for storing transaction data on free goods?
Thanks,
Juwin

Find the table number of the key combination of customer / material . & you can extract free goods condition records from this table.
Search in SE11 with the table number.

Regarding Condition record in CRM using field MATKL (Material Group)

Hi All
Currently we are working in SAP CRM 5.2 and it has been connected with backend ECC 6.0.
This scenario is about Pricing which has been maintained in ECC and inturn flows to CRM with few filters in place.
There are few customized Condition Tables in ECC with combination of Sales org./ material group for which discount has been maintained. A proper condition record is also available for this Condition table and it has been assigned to a access sequence and inturn assigned to a condition type.
All these procedures, condition types, access sequence has flown from ECC to CRM. And all the condition tables are active in IMG (Basic Functions / Pricing / Define Settings for Pricing / Create Condition Tables)
When i check in
(SAP menu / Master Data / Prices and Conditions / SAPCND/GCM - Maintain Conditions )
Application - CRM,
Maintenance group - PRODDISCOU,
Maintenance context - GCM
Here for the above mentioned combination when i select the Key Combination (Condition Table) and enter the customized table number (Sales org. / Material Group) iam getting a dump which says the following.
Error analysis
Short text of error message:
Implementation of Method ATTRIBUTE_CONVERSION for BAdI /SAPCND/ROLLNAME for filter MATKL is missing
Program............. "/SAPCND/CL_MNT_COND_MAINT_UI==CP"
Screen.............. "/SAPCND/SAPLCOND_MAINTAIN 0100"
Screen line......... 8
Information on where terminated
Termination occurred in the ABAP Program "/SAPCND/CL_MNT_COND_MAINT_UI==CP" -
in "ON_FCODE_SELECT".
The main program was "/SAPCND/GENERAL_COND_MAINT ".
In the source code you have the termination point in line 622
of the (Include) program "/SAPCND/CL_MNT_COND_MAINT_UI==CM005".
Please let me know the solution, Request you to do the needful aSAP.
Regards
*Ramesh*

Hi Ramesh,
Have you checked the following note?
Note 441083 - Transferring conditions for material group MATKL to CRM
Kind regards,
Johan Wigert

BAPI_PO_CREATE1 -- Condition Record filling

Similar Messages

Maybe you are looking for