Problem with condition type in BAPI_PO_CREATE1

Hi All,
I am uploading the data for txn ME21N through BAPI_PO_CREATE1.
Whenever i m testing this bapi it is giving PO no. but Codition types are not getting update neither on header level nor on item level.
Header Condition type and Condition value ,I am giving in Structures POCONDHEADER, POCONDHEADERX and Item Condition type and Condition value , i am giving in structures POCOND,POCONDX.
Thanx in Advance.
Regards,
Shiv Kant

Take a look in this example:
    ADD 10 TO v_item.
    e_poheader-comp_code   = t_cabec-bukrs.
    e_poheader-doc_type    = 'EC'.
    e_poheader-vendor      = t_cabec-lifnr.
    e_poheader-creat_date = sy-datum.
    e_poheader-created_by = sy-uname.
    e_poheader-item_intvl = '0010'.
    e_poheader-langu       = sy-langu.
    e_poheader-langu_iso   = sy-langu.
    e_poheader-incoterms1 = t_cabec-inco1.
    e_poheader-incoterms2 = t_cabec-inco2.
    e_poheader-currency   = t_cabec-waers.
    e_poheader-purch_org = v_ekorg.
    e_poheader-pur_group = t_saida3-ekgrp.
    e_poheader-pmnttrms   = t_cabec-zterm.
    e_poheader-telephone = t_cabec-telf1.
    e_poheader-sales_pers = t_cabec-verkf.
    e_poheaderx-comp_code   = 'X'.
    e_poheaderx-doc_type    = 'X'.
    e_poheaderx-vendor      = 'X'.
    e_poheaderx-creat_date = 'X'.
    e_poheaderx-created_by = 'X'.
    e_poheaderx-item_intvl = 'X'.
    e_poheaderx-langu       = 'X'.
    e_poheaderx-langu_iso   = 'X'.
    e_poheaderx-incoterms1 = 'X'.
    e_poheaderx-incoterms2 = 'X'.
    e_poheaderx-currency   = 'X'.
    e_poheaderx-purch_org = 'X'.
    e_poheaderx-pur_group = 'X'.
    e_poheaderx-pmnttrms   = 'X'.
    e_poheaderx-telephone = 'X'.
    e_poheaderx-sales_pers = 'X'.
    IF t_saida3-elem_pep IS NOT INITIAL.
      MOVE 'P' TO t_saida3-knttp.
    ELSEIF t_saida3-aufnr IS NOT INITIAL.
      MOVE 'F' TO t_saida3-knttp.
    ELSEIF t_saida3-kostl IS NOT INITIAL.
      MOVE 'K' TO t_saida3-knttp.
    ENDIF.
    t_poitem-po_item      = v_item.
    t_poitem-plant        = s_werks.
    t_poitem-short_text   = t_saida3-txz01.
    t_poitem-quantity     = t_saida3-menge.
    t_poitem-po_unit     = t_saida3-meins.
    t_poitem-acctasscat   = t_saida3-knttp.
    t_poitem-matl_group   = t_saida3-matkl.
    t_poitem-tax_code     = t_saida3-mwskz.
    t_poitem-order_reason = t_saida3-bsgru.
    t_poitem-indus3       = t_saida3-j_1bindus3.
    t_poitem-matl_usage   = t_saida3-j_1bmatuse.
    t_poitem-mat_origin   = t_saida-j_1bmatorg.
    t_poitem-item_cat     = t_saida-epstp.
    t_poitem-net_price    = t_saida3-netpr.
    t_poitem-price_unit   = t_saida3-peinh.
    t_poitem-bras_nbm     = t_saida3-j_1bnbmco1.
    t_poitem-PREQ_NAME    = t_saida3-requisitante.
     APPEND t_poitem.
    t_poitemx-po_item      = v_item.
    t_poitemx-plant        = 'X'.
    t_poitemx-short_text   = 'X'.
    t_poitemx-quantity     = 'X'.
    t_poitemx-po_unit      = 'X'.
    t_poitemx-acctasscat   = 'X'.
    t_poitemx-matl_group   = 'X'.
    t_poitemx-tax_code     = 'X'.
    t_poitemx-order_reason = 'X'.
    t_poitemx-indus3       = 'X'.
    t_poitemx-matl_usage   = 'X'.
    t_poitemx-mat_origin   = 'X'.
    t_poitemx-item_cat     = 'X'.
    t_poitemx-net_price    = 'X'.
    t_poitemx-price_unit   = 'X'.
    t_poitemx-bras_nbm     = 'X'.
    t_poitemx-preq_name    = 'X'.
    APPEND t_poitemx.
    t_schedule-po_item = v_item.
    t_schedule-del_datcat_ext = '1'.
    t_schedule-delivery_date = v_data.
    t_schedule-del_datcat_ext = 'D'.
    t_schedule-quantity = t_saida3-menge.
    APPEND t_schedule.
    t_schedulx-po_item = v_item.
    t_schedulx-del_datcat_ext = 'X'.
    t_schedulx-delivery_date = 'X'.
    t_schedulx-del_datcat_ext = 'X'.
    t_schedulx-quantity = 'X'.
    APPEND t_schedulx.
    t_account-po_item = v_item.
    t_account-gl_account = t_saida3-saknr.
    t_account-wbs_element = t_saida3-elem_pep.
    t_account-costcenter = t_saida3-kostl.
    t_account-orderid     = t_saida3-aufnr.
    t_account-gr_rcpt     = t_saida3-recebedor.
    t_account-unload_pt   = t_saida3-pdescarga.
    APPEND t_account.
    t_accountx-po_item = v_item.
    t_accountx-gl_account = 'X'.
    t_accountx-wbs_element = 'X'.
    t_accountx-costcenter = 'X'.
    t_accountx-orderid     = 'X'.
    t_accountx-gr_rcpt     = 'X'.
    t_accountx-unload_pt    = 'X'.
    APPEND t_accountx.
CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
      poheader         = e_poheader
      poheaderx        = e_poheaderx
      testrun          = ' '
    IMPORTING
      exppurchaseorder = v_pedido
    TABLES
      return           = t_bapiret2
      poitem           = t_poitem
      poitemx          = t_poitemx
      poschedule       = t_schedule
      poschedulex      = t_schedulx
      poaccount        = t_account
      poaccountx       = t_accountx
      potextitem       = t_textitem
      potextheader     = t_textheader.

Similar Messages

Problem with Condition Type in BAPI_QUOTATION_CREATEFROMDATA2 for Txn VA21

Hi All,
I am using BAPI_QUOTATION_CREATEFROMDATA2 for Sales Quotation by txn VA21.
In this txn,There are 22 condition types available in my system.
The problem is,it is updating every condition type twice.
Pls give me the solution.
Regards,
Shiv Kant

Hi,
I am giving billing document code, we are using BAPI to upload billing documents into SAP.
you can check pricing conditions code. we are using only two pricing condition types. our technical consultant hardcoded condition types.
wa_billingdata-salesorg = wa_bill5-sorg.
    wa_billingdata-distr_chan = wa_BILL5-dist.
    wa_billingdata-division = wa_BILL5-div.
    wa_billingdata-doc_type = 'ZSO5'.
    wa_billingdata-ordbilltyp = 'FX'.
    wa_billingdata-bill_date = wa_BILL5-BDATE.
    wa_billingdata-sold_to = wa_BILL5-CUSTNO.
*    wa_billingdata-price_date = WA_BILL1-BDATE.
   wa_billingdata-country = wa_BILL5-CNTRY.
    wa_billingdata-bill_to = wa_BILL5-custno.
    wa_billingdata-currency = WA_BILL5-CURR.
    wa_billingdata-wbs_elem = wa_bill5-wbsele.
    wa_billingdata-xblnr = wa_bill5-billno.
    wa_billingdata-zuonr = wa_bill5-invoiceno.
flag1 = 1.
endif.
translate wa_bill5-matdesc to upper case.
    SELECT MATNR FROM MARA INTO IT_MARA up to 1 rows WHERE MATNR = WA_BILL5-MATDESC.
            endselect.
    if sy-subrc = 0.
      wa_billingdata-plant = wa_BILL5-PLANT.
      wa_billingdata-NO_MATMAST = ' '.
      wa_billingdata-material = WA_BILL5-MATDESC.
      wa_billingdata-REQ_QTY = '1'.
      wa_billingdata-ACCTASGNMT = '05'.
   else.
       wa_billingdata-ACCTASGNMT = '05'.
       wa_billingdata-NO_MATMAST = 'X'.
       wa_billingdata-SHORT_TEXT = 'ADAGE MATERIAL'.
       wa_billingdata-TAXCL_1MAT = '0'.
       wa_billingdata-SALES_UNIT = 'EA'.
       wa_billingdata-material = WA_BILL5-MATDESC.
       wa_billingdata-REQ_QTY = '1'.
   endif.
flag = flag + 1.
    wa_billingdata-ref_item = flag.
    append wa_billingdata to billingdata.
    wa_conditiondata-data_index = flag.
     wa_CONDITIONDATA-cond_value = WA_BILL5-ADVERTISCOST.
    wa_conditiondata-cond_type = 'EK01'.
    append wa_conditiondata to conditiondata.
clear wa_conditiondata.
    wa_conditiondata-data_index = flag.
     wa_conditiondata-cond_value = WA_BILL5-COMM.
    wa_conditiondata-cond_type = 'ZCOM'.
    append wa_conditiondata to conditiondata.
clear wa_conditiondata.
IF TESTRUN IS INITIAL.
move-corresponding wa_bill5 to wa_bill2.
wa_bill2-status = 'P'.
append wa_bill2 to it_bill2.
modify zzbilling from table it_bill2.
commit WORK.
ENDIF.
REFRESH IT_BILL2.
endloop.
flag1 = 0.
flag = 0.
IF TESTRUN IS INITIAL.
CALL FUNCTION 'BAPI_BILLINGDOC_CREATEMULTIPLE'
*   EXPORTING
*     CREATORDATAIN         = creaord
*     TESTRUN               = 'X'
*     POSTING               = 'X'
    TABLES
     BILLINGDATAIN         = billingdata
     CONDITIONDATAIN       = conditiondata
*     CCARDDATAIN           =
*     TEXTDATAIN            =
*     ERRORS                =
      RETURN                = bapiret
      SUCCESS               = succ.
Regards,
Chandra

V-41 tcode error :Table 304 is not defined for use with condition type PR00

Hi All,
I am trying to create a BDC using the transaction V-41.
The first screen has fields:
ConditionType and Table, where I have to fill values ZPM1 and 800 respectively.
But as soon as I enter the tcode v-41 and say enter, the above mentioned fields are already having the values 'PR00' and ' 304'. Normally if you take an example fo t-code VA02, all fields are blank.
Then an error message is displayed:
Table 304 is not defined for use with condition type PR00
This behaviour is not allowing me to use the BDC feature.
Please advise me on why this is happening. What are the possible solutions I can use to clear these values programmatically?
Can anything be done via customizing?
Regards,
Namita.

Dear ILHAN ,
Well the problem you are facing is having the following solution:
Table 304 is not defined for use with condition type PR00
Message no. VK024
Diagnosis
The selected condition type does not fit in the condition table, that is the basis for the condition record. Alternatively the selected condition type is not included in the condition types that were selected on the selection screen or that are defined in the variant of the standard selection report.
Procedure
Úse F4 help to choose a valid condition type.
If this does not give you the required condition type, check in Customizing for condition types and the related access sequences.
In the condition maintenance also check Customizing for the selection report (pricing report), that you have selected in the navigation tree, using the standard condition table as a reference.
I hope this helps.
It has worked for me.
I gave it a try and what I am getting using the transaction V-41 is create Price condition (PR00) : Fast Entry.
Please award points if you find it useful.
Regards,
Rakesh

Scheduling Agreement With Condition Type Calc.

Hi All,
Can i have Scheduling Agreement With Condition Type Calc. as in PO Conditions as there are some calculation need to be made based on Excise.
Thanks in advance
Sapuser

Hi,
Condition in scheduling agreeement are time dependent where as condition in purchase order time independent so it's not possible to use.
Regards
Ravi Shankar.

Problems with letter type

Problems with letter type homepage www.JO-qigong.nl When I want to make another type it changes the whole page? Why?

Thank you for responding. I am sure that I selected the text. I don't do anything different than I did many times before. But if I change a text know, for exemple in the color Red, than other text, that I didn't selected, get a different text: bigger text or other color. In iWeb everything is OK, but when I publish it, than there are those grazy changes. I use iWeb for 3 years now and had no problems till now.
Is it because the software is not supported anymore by Apple, because you can not update the software anymore. It is a pitty, because I like iWeb. It is easy to work with.

Problem with mime type in web.xml file

Hi everybody,
I actually got a problem with mime types on Weblogic 6.0 under Linux.
I read the documentation so I added the next lines in the web.xml file in
the WEB-INF directory of my server :
<mime-mapping>
<extension>
doc
</extension>
<mime-type>
application/msword
</mime-type>
</mime-mapping>
<mime-mapping>
<extension>
ppt
</extension>
<mime-type>
application/vnd.ms-powerpoint
</mime-type>
</mime-mapping>
Why can't I retrieve a .doc or .ppt files with an internet browser correctly
? I get only text/plain ...
Can someone help me ?
Regards,
Alexis Berger

I am having the same problem with doc and xsl. I have added this
<mime-mapping>
<extension>xls</extension>
<mime-type>application/vnd.ms-excel</mime-type>
</mime-mapping>
<mime-mapping>
<extension>doc</extension>
<mime-type>application/msword</mime-type>
</mime-mapping>
to my web.xml. I even restarted the server. I still see doc and xsl in binary.
Is there some other setting that needs to take place?
I am using WL6.1 with fixpack 1.
I can see the doc and excel files in the browser if I don't go through the weblogic
server. That just confirms it's not my browser.
Kumar Allamraju <[email protected]> wrote:
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
It works fine for me in 6.1 SP1.
 
If the following doesn't work , can you
 try application/winword instead of application/msword?
--
 Kumar
Siming Mu wrote:
<blockquote TYPE=CITE>Hi,
I setup in my web.xml a mime mapping as follows,
<mime-mapping>
 <extension>doc</extension><mime-type>application/msword</mime-type>
 </mime-mapping>
When I specify a test.doc url, the doc file appears in my browser
as
binary data
 instead of download.
Please reference change request 055002, which decribes this problem.
According
 to edocs, it has been fixed in wls6.1sp1.
But I am seeing it fixed. Am I doing anything wrong? Thanks.
Siming</blockquote>
</html>

How I tie the formula with conditions type?

Hi,
Than create the formula with tcode O3I7:
1) how I tie the formula with conditions type?
2) how I tie the conditions type with the formula with Calculation Schema?
help me, please.
thanks
Edited by: celeste ziantoni on Feb 5, 2008 6:45 PM

Hello,
Pricing formula is created using transaction VOFM. It is tied to the condition types in Pricing Procedure definition in Alternate Calculation Type column. For Pricing procedure, the menu path is SPRO->Materials Management->Purchasing->Conditions->Define Price Determination Process->Define Calculation Schema.
Thanks,
Venu

How do fix problem with iPages - type does not enter - ?

How do I fix this problem with Pages - type from keyboard does not enter ? If I need to re-install, How do I do that?

Hello DonAndNorma,
You may need to uninstall, then reinstall the Pages application. Steps for doing so can be found in the article linked below.
OS X Mavericks: Install, update, and uninstall apps
http://support.apple.com/kb/PH14299
Cheers,
Allen

PO BAPI Problem in condition types

Hi,
I am facing a strange problem in creation of PO through "BAPI_PO_CREATE1".
In the Item condition internal table, I am passing the condition types.
The PO is getting created successfully.
Eg. I pass conditions and their values as follows:
PB00 : 1000
ZB00 : 1000
FRB1 : 1000
The PO is created successfully and we can check the prices updated properly.
Now,
When I create a second PO with the same values, the prices are taken from the last PO and the prices from
my code(which are passed through BAPI) are added to the last value.
If I run the program with the same values as above, the PO is created with the values 2000.
Third time it is 3000 and so.
The value from the last PO is coming into the new PO.
Please advise me if anything missing.
My code is below::
================
*& Report ZTEST_PO
REPORT ZTEST_PO.
data : HEADER like BAPIMEPOHEADER .
data : HEADERX like BAPIMEPOHEADERX .
data : POITEM like BAPIMEPOITEM occurs 0 with header line.
data : POITEMX like BAPIMEPOITEMX occurs 0 with header line.
data : POSCHEDULE like BAPIMEPOSCHEDULE occurs 0 with header line.
data : POSCHEDULEX like BAPIMEPOSCHEDULX occurs 0 with header line.
DATA : RET LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA : ret1 like bapiret2.
Data PO like BAPIMEPOHEADER-PO_NUMBER.
data : pocond like BAPIMEPOCOND occurs 0 with header line.
data : pocondx like BAPIMEPOCONDX occurs 0 with header line.
*pocond-CONDITION_NO = '00000'.
pocond-itm_number = '000010'.
pocond-COND_ST_NO = '001'                                   .
*pocond-COND_COUNT = '1'.
pocond-COND_TYPE = 'PB00'.
pocond-COND_value = '500'.
pocond-CURRENCY = 'EUR'.
pocond-CURRENCY_ISO = 'EUR'.
pocond-CHANGE_ID = 'I'.
APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '10'                                   .
*pocond-COND_COUNT = '2'.
*pocond-COND_TYPE = 'PBXX'.
*pocond-COND_value = '555'.
*pocond-CURRENCY = 'EUR'.
*pocond-CURRENCY_ISO = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '20'                                   .
*pocond-COND_COUNT = 0.
*pocond-COND_TYPE = 'ZB00'.
*pocond-COND_value = '666'.
*pocond-CURRENCY = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
**pocond-CONDITION_NO = '00000'.
*pocond-itm_number = '000010'.
*pocond-COND_ST_NO = '30'                                   .
*pocond-COND_COUNT = 0.
*pocond-COND_TYPE = 'FRB1'.
*pocond-COND_value = '777'.
*pocond-CURRENCY = 'EUR'.
*pocond-CHANGE_ID = 'U'.
*APPEND POCOND.
*pocondx-CONDITION_NO = '00000'.
POCONDX-ITM_NUMBER = '000010'.
POCONDX-COND_ST_NO = '000'.
*POCONDX-CONDITION_NOX = 'X'.
*POCONDX-COND_ST_NOX = 'X'.
POCONDX-ITM_NUMBERX = 'X'.
*POCONDX-COND_COUNT = 'X'.
POCONDX-COND_TYPE = 'X'.
POCONDX-COND_value = 'X'.
pocondX-CURRENCY = 'X'.
*pocondX-CURRENCY_ISO = 'X'.
pocondX-CHANGE_ID = 'X'.
APPEND POCONDX.
HEADER-COMP_CODE = 'TF01'.
HEADER-DOC_TYPE = 'DMPO'.
HEADER-VENDOR = '0000000317'.
HEADER-LANGU = 'EN'.
HEADER-PURCH_ORG = '1001'.
HEADER-PUR_GROUP = '110'.
HEADER-CURRENCY = 'EUR'.
HEADER-DOC_DATE = '22.10.2007'.
HEADER-REF_1 = '999999999999'.
HEADERX-VENDOR = 'X'.
HEADERX-PURCH_ORG = 'X'.
HEADERX-PUR_GROUP = 'X'.
HEADERX-REF_1 = 'X'.
POITEM-PO_ITEM = '00010'.
POITEM-MATERIAL = '00042199730L'.
POITEM-PLANT = '1000'.
POITEM-STGE_LOC = '1030'.
POITEM-MATL_GROUP = '01'.
POITEM-QUANTITY = '10'.
POITEM-PRICE_UNIT = 500.
poitem-calctype = 'C'.
append POITEM.
POITEMX-PO_ITEM = '00010'.
POITEMX-MATERIAL = 'X'.
POITEMX-PLANT = 'X'.
POITEMX-QUANTITY = 'X'.
POITEMX-PRICE_UNIT = 'X'.
append POITEMX.
POSCHEDULE-PO_ITEM = '00010'.
POSCHEDULE-DELIVERY_DATE = '30.10.2007'.
append POSCHEDULE.
POSCHEDULEX-PO_ITEM = '00010'.
POSCHEDULEX-PO_ITEMX = 'X'.
POSCHEDULEX-DELIVERY_DATE = 'X'.
append POSCHEDULEX.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
    poheader                     = HEADER
    POHEADERX                    = HEADERX
POADDRVENDOR                 =
TESTRUN                      =
MEMORY_UNCOMPLETE            =
MEMORY_COMPLETE              =
POEXPIMPHEADER               =
POEXPIMPHEADERX              =
VERSIONS                     =
NO_MESSAGING                 =
NO_MESSAGE_REQ               =
NO_AUTHORITY                 =
NO_PRICE_FROM_PO             =
IMPORTING
   EXPPURCHASEORDER             = PO
EXPHEADER                    =
EXPPOEXPIMPHEADER            =
TABLES
   RETURN                       = RET
   POITEM                       = POITEM
   POITEMX                      = POITEMX
POADDRDELIVERY               =
   POSCHEDULE                   = POSCHEDULE
   POSCHEDULEX                  = POSCHEDULEX
POACCOUNT                    =
POACCOUNTPROFITSEGMENT       =
POACCOUNTX                   =
   POCONDHEADER                 = POCOND
   POCONDHEADERX                = POCONDX
    POCOND                       = POCOND
    POCONDX                      = POCONDX
POLIMITS                     =
POCONTRACTLIMITS             =
POSERVICES                   =
POSRVACCESSVALUES            =
POSERVICESTEXT               =
EXTENSIONIN                  =
EXTENSIONOUT                 =
POEXPIMPITEM                 =
POEXPIMPITEMX                =
POTEXTHEADER                 =
POTEXTITEM                   =
ALLVERSIONS                  =
POPARTNER                    =
POCOMPONENTS                 =
POCOMPONENTSX                =
POSHIPPING                   =
POSHIPPINGX                  =
POSHIPPINGEXP                =
NFMETALLITMS                 =
if RET-type NE 'E'.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          WAIT   = 'X'
        IMPORTING
          RETURN = ret1.
write : ' PO Created : ', PO   .
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
        IMPORTING
          RETURN = ret1.
    ENDIF.
================

Any input??

Problem in Conditions while using BAPI_PO_CREATE1

Hi All
I am using BAPI_PO_CREATE1 to create purchase Order. When I am changing calculation type for condition type's system not picking the correct amount through BAPI.
For e.g. for condition type 'FRB1' (Freight Value) I have maintain the amount 10.00 in condition value for calculation type 'B' (fixed amount). But when I pass calculation type 'A' i.e. Percentage, BAPI overwrites the amount to 1.00%.
I Want to pass the amount 10.00 as it is with calculation type '%'. Kindly suggest how to do it.
Regards,
Pradip

Hi All
I am using BAPI_PO_CREATE1 to create purchase Order. When I am changing calculation type for condition type's system not picking the correct amount through BAPI.
For e.g. for condition type 'FRB1' (Freight Value) I have maintain the amount 10.00 in condition value for calculation type 'B' (fixed amount). But when I pass calculation type 'A' i.e. Percentage, BAPI overwrites the amount to 1.00%.
I Want to pass the amount 10.00 as it is with calculation type '%'. Kindly suggest how to do it.
Regards,
Pradip

Pricing error with condition type HI02

Hi Friends,
I have problem in pricing procedure for customer hierarchy condition type HI02. I have created the condition node i.e.6222 and assigned customer 1500 and i also maintained the condition record for the same and also put in the pricing procedure as well. Now while i am creating sales order the condition type HI02 is not coming automatically rather i am able to put the same manually. I want the system should pick the condition type HI02 automatically. Please suggest me IMG setting which i sould maintain for customer hierarchy pricing.
Thanks in advance,
Bharat B

Dear Barath
You are right
HI02 is a item condition type only used for customer hierarchy discounts and the access sequence for the same is HI02 with condition table 065 that is customer hierarchy/material and the same is positioned in V/07 in the access sequence details in seven consecutive steps (the same condition table in all the seven steps) but the field in each table differing
The field in table 065 which is positioned in no 1 is HIENR 01
The field in table 065 which is positioned in no 2 is HIENR 02
The field in table 065 which is positioned in no 3 is HIENR 03
and the most important thing here is exclusive indicator ticked in all the steps exept the seventh step
That means if at hierarchy level 1 system finds a record then it stops searching
I have a feeling that your access sequence alignmemt must be wrong somewhere and check for exclusive indicator marking
HI01 is a item condition type only used for customer hierarchy discounts and the access sequence for the same is HI01 with condition table 064 that is customer hierarchy and the same is positioned in V/07 in the access sequence details in seven consecutive steps (the same condition table in all the seven steps) but the field in each table differing
The field in table 064 which is positioned in no 1 is HIENR 01
The field in table 064 which is positioned in no 2 is HIENR 02
The field in table 064 which is positioned in no 3 is HIENR 03
and the most important thing here is exclusive indicator ticked in all the steps exept the last step
That means if at hierarchy level 1 system finds a record then it stops searching
I have a feeling that your access sequence alignmemt must be wrong somewhere and check for exclusive indicator marking
Moreover importantly if there is condition type in a PP then if a condition record is maintained if the same is not picked up in sales order then analysis has to give some hint and what is the hint you are getting
Regards
raja

Standard Report with Condition Type and Condition Records

Hello to all,
Is there any standard report available in which Condition Type and Condition values are displayed in either column or row format? The selection criteria can be either Quotation, Contract, Sales Order, Delivery, Invoice or Billing. Thanks anyways...

Hi Huzefa,
Pls check the relevant table where the condition records are stored. then do a query with that condition table and KONP. say for eg: condn type ZINV,ZMRP gets stored in condition table A821, then combine A821 and KONP, u can input condition type and get the values........................
go to vk13, display and click on layout, u will able to see the condition table.
Rgds,
Anitha J

Problem with numeric types in Abap Proxy

Hello,
We are having problems with some abap proxy calls. When a numeric type is filled with 0 the node it´s automatically removed and no value it's recived in XI. The only way I have found to avoid this problem it's to define the field with type string or change the cardinality to 1..1 instead of 0..1. It's there any way to maintain the type and the cardinality?? Maybe with a pattern??
Regards,
Alberto Pla.

Hi Alberto
I had this problem, and I decided to use xsd:string instead of xsd:integer. This will solve the issue.
Anyway.. check this note:
[Note 1242795 - Mapping of XSD default values by ABAP Proxy Generation|https://service.sap.com/sap/support/notes/1242795]
Regards
Francesco

Problem with file type... some files have been changed to folders... Help !

Hello,
I have problem with some files that are located in Library / Quicktime.
I have 7 files in that folder and all are .component files.
3 of them used to look like a lego block :
DivX Encoder.component
macam.component
MayaIFF.component
But today, I have accidentally change them into folders (and I don,t Know how...) So instead of having thoses 3 files with the lego block icon , I have 3 folders and If I click on thoses folder, It open like a standard folder, so I see the "content" folder inside them...
How can I change it back to the .component file type they should be... I know how to change the type of a file, but since they are now folders, there's no "file Type" associated with them (right click / infos)...
Help !

There are lots of things that are in fact folders, but the Finder treats them as "files"--in the sense that normally when you select one you cannot see the contents of the folder. One way this is done is by the use of certain extensions, for instance .app, .pkg, .mpkg, .bundle and .component all tell the Finder to NOT display the folders as folders. If you do a GetInfo on them and the name is still "whatever.component" and the Kind: Component is still showing, and you haven't noticed any problem with QuickTime, then don't worry about it.
Those are all third party QT components. If they aren't working, you may have to reinstall them from the original source.
Francine
Francine
Schwieder

Problem with field type STRING in table

Hi Experts,
I am new to ABAP. I have created a new transparent table which hold error info. One of the field has to store data of size about 1500 char.
Since CHAR type is not acceptable for this field So I gave STRING type. Now when I try to create a TABLE parameter in a RFC enabled functional module using "LIKE YERROR" Then I get a error:
"YERROR must be a flat structure. You cannot use internal tables, strings, references, or structure as component"
Why is this error? How to resolve it? Is it because I have used a field of type STRING in the table? If this is the problem then what other type can I use?
What are other know problems with using STRING type?
Please help!
Thanks
Gopal

Hi,
Try to declare it as type LCHR , it can hold up to 32000 chars.
Regards
vijay

Problem with condition type in BAPI_PO_CREATE1

Similar Messages

Maybe you are looking for