CONDITION TYPE PROBLEM
Hai All,
I have a business scenario mentioned in the following procedure.
Work done for HVAC = 1000
Work done for ELECTRICAL = 2000
Work done for PLUMBING = 3000
Total = 6000
Value of Material on site = 3000
Advance = 2000
Retention = - 1000
So total = 600030002000-1000= 10000
Here the main logic is value of material on site ,advance and retention is on the whole amount i,e = 6000
it should not distribute individually .
Here I maintained the work done as the item conditions and the value of material on site,advance ,retention as header at one time and keeping as header group condition as another time,but the system is distributing the amount in respective values.
Where exactly the settings to be done .
It does not served my purpose.
Please help for above scenario.
Regards,
Kalyan
Well, you were close. For the first condition type
you could enter SH_TYPE in Expression 1 and ADSL in
Expression 2 (no quotes).
For a SQL Expression or PL/SQL Expression condition
you would enter :SH_TYPE = 'ADSL'Somehow both ways did not work.
First I tried first way. The database contains two records:
select sh_id, sh_type from shops;
returns
22 IPSEC
1 ADSL
I click on P7_SH_ADSL_IP_MODEM (because this is the field I want to edit if SH_TYPE is set to ADSL), scroll down to Condition Type, choose "Value of Item in Expression 1 = Expression 2", set Expression 1 to SH_TYPE and Expression 2 to ADSL without quotes. Then I try to edit #1 record. It has SH_TYPE = ADSL, I checked that with simple sql query above. But when I reload the edit page I don't get a field for SH_ADSL_IP_MODEM, no matter what SH_TYPE contains. If I change Conditon Type to "Value of Item in Expression 1 != Expression 2" then I get that field all the time, again no matter what SH_TYPE contains.
The same happens with SQL Expression and PL/SQL Expression.
Similar Messages
-
Hi ,
I have created rebate condition type,access sequence and the rebate table where i use field "Material group 4" which was not in standard .So i added that field in the standard table by including ,And it works fine .I have done every step for making rebate config .
Ex.
Maintain subtotal 7 in pricing procedure .
Access Sequence 1(relevent for rebate).
Acc key :ERB,& ERU.
Condition type : condition class :C.
and upto billing its works fine .and the rebate condition type is appear in billing document only (assigning req.24) .
But the issue is when i realease the billing document to accounting ,the rebate condition type got vanish .But when i create the billing and have a look by VF02 this condition type shows with proper value .
I got puzzle . Am i missing something for config .....
Need urgent halp ...........
Thanks in Advance .......
Regards,
Abhijit....Hi ravi
The infostrucuture S136 is related to bonus buy extension.So if you activate it and if you extend the rebate date then you need to update the infostructure S136.But it will be in updating mode only.
But one thing to tell is there is no link to activate Bonus buy in your problem
So in OMO1 double click S469 change to synchronous updating.then your problem will be solved
If you are working at any server , then first of all check it in the sandbox server and then work ,so that it wont affect the development server
Regards
Srinath -
Pricing Condition Type Problem !!
HI
Pricing condition for CVD was maintained as fixed value(calculation Type) originally. Client wanted it to be percentage basis. I changed it to % basis. It was wrking fine. But today again when a PO was made for same material .... the CVD was coming as fixed value and not % basis. Checked the M/06 conditions for CVD its still % calculation type. material price was picked from info record. all was done on dev server.
can any one guide why itshappening like this
Thank youHi,
CVD condition type is usually maintained as %age basis only.
the info record will store the the last PO history. if the combination of material, vendor is found , the access sequence will pick the condition record.
keep the same material and try will another vendor , this will not happen the system will pick the %age basis only.
check your info record?
check what you have maintained in MEKI for the condition type for CVD.
regards
Rajesh -
hello Folks
i tried to have the CST and VAT calculation running form the customer master record, but i could not finish it.
i created two conditions types, ZCST, ZVAT & with proper access sequence and
placed the condition types onto my tax procedure.
Then assigned my tax procedure to the country.
when i then go to SD - basic functions- taxes and clicked on tax determination rules ,
here am trying to assign ZCST and ZVAT condition type to the Country
Getting an error Message
Entry V ZVAT does not exist in T685A - Check your entry,
how should i go about it.
Please revert back quickly, this need a resolve around
thanks ,Hi,
I think you created new condition types at FI level i.e. Tax Pricing Procedure, also create the same condition type at SD level i.e. SD Pricing Procedure should have the condition type. Create the same condition types under pricing at IMG and then try assigning the condition type to the country.
The error you said is coz of the fact the particular table dosen't have the value....
Kindly reward if it helps.
Regards
Harsh -
Anyone help the condition type problem
Hi,
My requirement is if ZFI6 having values then it will display the ZFI6value no need no activate ZFI4 and ZFI3.
if ZFI6 having no values ZFI4 having value then it display ZFI4 only no need no activate ZFI3 and ZFI6.
if ZFI6 having ZERO then ZFI4 having ZERO so need to activate ZFI3 only.
i developed the below coding but its not working correctly anyone plz explain how to solve this issue.
READ TABLE XKOMV INTO L_XKOMV
WITH KEY
KSCHL = 'ZFI6'.
IF sy-subrc = 0.
XKOMV-KINAK = 'X'.
MODIFY XKOMV TRANSPORTING KINAK WHERE KSCHL = 'ZFI4'.
endif.
point will be sure.
VijaiHi Vijaya,
Try this
READ TABLE XKOMV INTO L_XKOMV
WITH KEY
KSCHL = 'ZFI6'.
IF SY-SUBRC = 0.
XKOMV-KINAK = 'X'.
MODIFY XKOMV TRANSPORTING KINAK WHERE KSCHL = 'ZFI4' OR KSCHL = 'ZFI3' .
CLEAR XKOMV.
ELSE.
READ TABLE XKOMV INTO L_XKOMV
WITH KEY KSCHL = 'ZFI4'.
IF SY-SUBRC = 0.
XKOMV-KINAK = 'X'.
MODIFY XKOMV TRANSPORTING KINAK WHERE KSCHL = 'ZFI6' OR KSCHL = 'ZFI3' .
CLEAR XKOMV.
ELSE.
XKOMV-KINAK = 'X'.
MODIFY XKOMV TRANSPORTING KINAK WHERE KSCHL = 'ZFI3'.
CLEAR XKOMV.
ENDIF.
ENDIF.
Regards,
Satish -
Problem with pricing condition type in case of proforma invoicing
Hello All,
the problem is related to a pricing condition type in case of proforma invoice where the details are as follows -
Name of Condition Type - ZADC - Add 10% on Cost Access seq. Z038 Diff
Plus/minus A Positive
Cond. class - A Discount or surcharge
Calculat.type - A Percentage
Cond.category - Blank
Manual entries D Not possible to process manually
Amount / Percent - Checked
Item Condition - checked
Scale Basis - Quantity
Currency Conversion - Checked
Quantity Conversion - Checked
This condition type has been kept as statistical in the pricing procedure. Still in the proforma invoice the condition type is not getting reflected automatically , whenever I am updating with " carry out new pricing " option the condition type is getting populated.In case of other commercial invoices this very condition type is getting populated automatically without any updates.Along with this point to be noted is that the Condition type in which the actual costi is captured has been kept active.
What more needs to be configured or what are the changes to be done to populate the condition type automatically as statistical during the time of proforma invoicing?
Thanks & Regards
Priyanka MitraHi,
Kindly do the pricing analysis and check whether you have the following error such as
Inactive condition type because of subsequent price,
Regards,
Ravi -
Problem in Sales Order with specific condition type.
Hello Experts,
I'm facing a problem in sales order creation for a specific condition type.
the actual scenario is as below,
We have created a new condition type for special discount.This condtion type is applicable only for specific sales channels.Also the discount percentage has to fetched from a custom table.
To achieve this I've written a user exit "RV64A999"
In the FM, i've calculated the subtotal and fetched the discount percentage and calculated the discount amount. After implementing this, the SO were been created properly. for all the line items the discount amount was getting calculated properly.
But then I added a condition at the top of code in exit that the calculation for the new condition type should happen only for selected sales channels.
But after adding this condition in code, i'm facing problem. Now when I create/ change any SO, the discount amounts are getting calculated incorrectly. I'm getting discount amount even if the line item subtotal amount is zero (0).
Any help or pointers reagrding this issue will be very helpful and highly appreciated.Hi ..
Check your config. again or debug the routine code with your ABAPer and find the problem area.
-Maharshi -
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 of DIFF (Rounding Off) Condition Type in Sales Pricing Procedure
Hi All,
This problem is related to Sales Order. The system is not picking up a condition type in the pricing procedure.
For example when I am raising a sales Order where the Trade Price is being calculated with the help of a Alternative Calculation Type , Subtotal 1 , X in the the Print column and Posting Key ERL are assigned to it.Here in the end the condition type DIFF is not getting populated in the pricing though it is maintained in the pricing procedure. When I am checking in the pricing analysis the error message and its detailed description which is shown as follows -
DIFF 011 Condition ignored (requirement 013 not fulfilled)
The requirement 1. was assigned to this condition in the pricing procedure. This requirement was not met in the preliminary condition step, and so the condition was excluded from further processing.
You can use Additional information to display the requirements used.
Now considering the above scenario please suggest to attain my requirement.
Thanks & Regards
PriyankaDear Priyanka,
The "reqt" field in the pricing procedure basically tells d system that the routine mentioned in this field is a sort of prerequisite without fullfilling of which the associated condition type will not get xecuted.
In ur case u have selected "1" which is for condition types A001, B001 etc used in "material listing / xclusion" function.
For condition type DIFF, the correct value is "13" i.e "Rounding as per T001R".
So just replace "1" with "13", things will b fine.
Please close the thread if answered.
regards
Param -
Problem in Copying Pricing Condition Type
Hi All,
This problem is regarding copying pricing condition type in Sales Order. The problem is given below with an example -
Qty of Material A - 10 PC.
Condi Type Amount Currency Per UOM Condition value Currency
ZP06 100 INR 1 PC 1000.00 INR
ZP07 2 INR 1 PC 20.00 INR
ZP08 98 INR 1 PC 980.00 INR Statistical
ZP01 98 INR 1 PC 980.00 INR Mandatory with ERL A/c Key Active
The condition types ZP06 & ZP07 have access sequence maintained for them and ZP08 has been derived deducting ZP07 from ZP06.
I want the above mentioned scenario where the values of Condition Type ZP08 which is a Statistical Condi Type will be copied exactly & entirely to condition type ZP01 where It will remain active alongwith posting key ERL.
I have tried copying it by 100 % copy but the value is getting changed as 100% instead of 98 INR.
Considering the above scenario please suggest some soluitons.
Thanks & Regards
PriyankaHi Tarpan,
First of all thanks for checking my post.
In the problem I am not looking for the value of ZP08 to be maintained manually.I want the system to copy the exact details of ZP08 to ZP01 entirely where the condition type ZP01 will remain active alongwith the posting key ERL.
I have tried copying the condition type ZP08 by using 100% copy of condition type but in ZP01 the resultant value becomes 100% in place of 98 INR.
Please suggest some solutions.
Thanks & Regards
Priyanka -
Same condition type on header and item level = printing problem
Hi
I have a customer using some condition types on both item level and header level in quotations, orders, invoices ...
In the pricing procedures it is customized (V_T683S-DRUKZ) that the conditions must be printed on header level (that is at the bottom of the documents).
My job is to make the Smartform to print the documents, and I want it of course to be as close to SAP standard as possible.
SAP standard will print these conditions on header level even if the conditions are at item level, but my customer wants the conditions created on header level to be printed on header level and conditions created on item level to be printed on item level.
I'm no pricing expert, so my question is:
Will it be fair if I tell the customer that using the same condition types on header and item level is bad practices - or at least bad karma?
Best regards
Thomas Madsen NielsenHi Shiva Ram and Madhu
I have no problem understanding header vs. item conditions, so I really don't see anything in oss note 876617, that is relevant in this case.
Madhu - I do not agree that everything is fine. My issue is that I want to stick as closely to SAP standard customizing as possible. In SAP standard customizing of a condition type you can use the flag V_T683S-DRUKZ to determine if the condition should be printed on header OR item level - you can not choose both header AND item level.
I have a SAP standard smartform using two functions modules for reading header and item conditions. RV_PRICE_PRINT_ITEM and RV_PRICE_PRINT_HEAD. These function modules are based on the DRUKZ customizing flag and a condition marked for printing on header level will be supplied by RV_PRICE_PRINT_HEAD even when the condition is on item level.
My point is: SAP standard customizing does not support printing of same condition on both header and item level. I can of course write tons of code to work around this problem, but that would be bad practices -
Problem with multiple condition type for VAT &CST
Hi,Gurus,
pl. suggest the procedure for the following problem.we configured seperate pricing procedures for our product material and scrap material.We have configured same condition types for VAT(ie.condition type:ZVAT) and CST(cond type:ZCST), in both pricing procedures. Now We want to maintain seperate condition types for VAT and CST for pricing procedure for Product material and Scrap material. I have created two new condition types for scrap sales ZSCT- cst for scrap and ZSVT-vat for scrap by copying the same from existing conditions ZCST & ZVAT, and the same is included in the scrap pricing procedure. And also maintained OB40,OBCN,OVK1,OVK3,OVK4, FTXP,FV11 and VK11.
now I am facing the following problems.
1. while creating the Material master & customer master, in tax category sub screen all conditions i.e. conditions defined for product material( ZCST,ZVAT) and defined for scrap material (ZSCT, ZSVT) displaying and these are compulsory fields.
2. While creating the sale order for scrap material, system is considering the TAX classes from ZVAT/ ZCST (defined for product material) and taking the condition value from the condition type ZSVT/ ZSCT with the TAX class values of ZVAT/ZCST.
Now I would like to know is there any procedure to assign the Material type and Customer Account group to Tax category.
Thanks & Regards
samHello Sam,
The Access Sequence Assigned to your New Condition types ie, ZSCT and ZSVT are same as the Previous Condition type ZVAT and ZCST.
After Adding new condition type in the Tax category in the Masters you have to take care of the Sequence of the Condition type.
If ZSCT and ZSVT is on the 3rd and 4th number in the masters the Condition table you are using in the access sequence should have fields Taxclassification3-Customer and taxclassification3- material. For ZSCT
Likewise Taxclassification4-Customer and taxclassification4- material. For ZSVT
Please add New Condition table in the access sequence with the required Field
And next when you are maintaining the condition record for say ZSCT you will have to maintain condition record for the condition table which has Taxclassification3-Customer and taxclassification3.
In Document the values will be flown correctly after changing this.
Hope I have Solved your Query.
If any Doubt please revert.
Regards,
Rohit Dongre -
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 KantHi,
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 -
Problem with JECS and S&H cess condition type
Dear Experts,
According to client requirement, I have done pro-forma delivery *** excise invoice. Then I have done J1IIN- Excise invoice.(Account doc created). After that I have done F2 commercial billing with reference to delivery. Here if I include only 'basic excise
duty' condition type, getting no problem in FI posting. But if I include Ecess (JECS) and S&H cess (JA1X) condition type, then I can't post the commercial invoice into FI . An information message is coming, "no accounting doc generated". and the status in the billing document is "error in accounting interface". I have done all settings of account determination of CIN. Still getting this error. Please help me to overcome the problem.
Thanks in advanceDear Prashanth,
I have maintained 1. Account key EXD for JEXP, JECS and JA1X condition types. 2. Maintain account determination in CIN. 3. I have also maintained Tax code (A4, AC etc for VAT and CST) and maintained the condition record with tax code in vk11 also.
Should I maintain VKOA with EXD account key with KOFI and KOFK? I maintained previously EXD in VKOA also but still Im stuck in that problem. so I deleted from VKOA. I tried to post through VF02. at that time it is showing a message "Error in account determination : table T030K key BPIN EXD. Message no. FF709". but for JEXP I can post to FI without any error. I tried to search in that forum about the error. but didnt get any solution.please advice me.
Edited by: neel06 on Apr 30, 2011 9:41 AM -
Problem in Pricing Condition Type : In Service Confirmation
Hi,
I am trying to create Service Confirmation from Sevice Order. I am tring to edit service Item details.
I assigned valuation type as "Saturday". As per the actual result, one condition type(ZS13) for surcharge should get added in Item Pricing details. But, it is not getting added.
Can you plesse tell me, what configuration I need to do to add ZS13(condition type) automatically, when I select, valuation type.
Thanks,
Sandeephi,
Please check whether the condition type ZS13 has access sequence assigned having the condition table with Valuation Type as one of the fields.
Also check whether the accessses above this condition table are not exclusive.
The pricing trace may help you to analyse why this condition is not determined.
regards,
Chait
Maybe you are looking for
-
Time Machine no longer backing up from Macbook Pro
I've been successfully using Time Machine to backup my Macbook Pro via my wireless network for a couple of years. I was also using it to backup my wife's Macbook Pro until she had to be away for a while. While she was away she used a Passport backu
-
My old computer recently crashed, and so i've bought this windows laptop (which i'm using now). I have an iPod classic (latest model) and am fearful that if I retrieve my account on my new laptop, it'll delete all the information, 1,3000 songs and mu
-
Recover database when losing all the controlfile
I read theBackup and Recovery Advanced User's Guide of 10g R2. I can't quit understand a scene in Restore Control File from Backup After Loss of All Current Control Files Table 18–1 Scenarios When Control Files Are Lost When the status of onlin log i
-
The Adobe InContext Editing service will undergo scheduled maintenance starting on Saturday Oct 31 at 7pm PDT and end Sunday Nov 1 at noon PST. However, the service will be available during this time. The only area affected by this outage will be the
-
Demo Avail elsewhere for download!
Demo should be avail here soon I would think as now avail elsewhere for download already.