Header condition type should not be editable at item level

Hi gurus,
could you please help me with the following question.
Our requirement is to provide header discounts manually at header level which should not be editable at item level. So I've created condition type as Header condition.
When we manually add this condition at header level in Sales order, it is copied to the item level and is not editable there.
But after saving the SO, we find that the header discounts appearing at the item level becomes editable.
Kindly advice how to make the condition type as non-editable at item level.
Thanks in advance.
Sunny.

hi Sunny,
please check your condition type for discount in section 'Changes which can be made', wheather it used only for the header level or item level or both of it.
if you want to make the condition is not editable in item level, then you must made the condition type just for the header level.
beside changing the configuration in the condition type, you can protect it via BADI but it needs more programming.
if you insist to use the BADI, you can made the implementation of class CRM_ORDER_FIELDCHECK BADI
hopes it helps
cheers

Similar Messages

Header condition type value not displayed in sales order output

Hi gurus,
I have observed a strange issue regarding a header condition in a sales order.
we have a set up like following:
1. If the Header condition XXXX is used in sales Order then this value should be printed on sales order output.
2. If the Header condition mentioned in above point is not maintained in sales order it should print the total price of all line items.
Though i have maintained the header condition value in Sales Order Header its not displayed in SO output.
That is , I have a sales order and it has one HEADER condition type entered with 3500 USD.
In fact this value is used for some business purpose and is being printed on the sales order output for a specific output type.
But where as in a sales order this header condition value is not getting printed on the output though I am using same data as of the sales order which is having the header condition value printed on its output.
According to business,we must have the header condition value printed on sales Order output.
Please suggest how to proceed.
Thanks in advance.

Not sure if you are using costom smartform to print invoice, if yes then ask developer to debug and find the root cause and fix it.
You might need to give him condition when it shuld be printed and when not.
You can take reference of another output type for which it is printing

Standard Condition type used for Manual freight at item level

Hello Gurus
Can you please tell me the standard condition type used for entering freight manually at header as well as item level.
Warm Regards
Prashant Joshi.

Prashanth,
The freight Conditions that we use in Sales are two types
HD00 - Header Level, wherein we have no access sequence
KF00 - Item level, Wherein we have access sequence KF00 - Freight
But you want the condition types to be maintained manually, then you need item details screen of the respective condition type HD00/KF00 using Tcode V/06.
Inside that Manual entry as "C". Similarly you need to maintain or activate "Manual" Indicator in pricing procedure. Then you can enter the freight Manually.
Note:
The difference In applying at the header level and item level is if you enter freight value at the header level it is applicable to all items in the item level. But if you want to apply freight we can give freight to each item or selective item.
Regards
Sathya

Header Condition types

Dear Fnds,
I created 2 Header condition types ...in PP
Whenever i create Sales Order...these 2 condition types are Comming into Sales Order item Condition and Header Condition Tabs...but i need to maintain only at Header level
What could be the Prob?
Thanks in Advacne
Rej

Hi
How come the Header conditions are coming in the Sales order automatically.
Remember, Header conditions are always mannual there are not determined automatically , they do not contain Access sequence.
You have to enter those in the Sales document at Header level.
In the condition type (V/06), mark the condition type as "Header condition", remove the any activation from "Item condition" check box.
Remove the Access sequence if any you have specified.
In the Pricing Procedure mark the condition types as "Mannual".
Now, in the Sales order, go to the Header details > condition screen and enter the Header condition mannually with the amount as required by you.
It will be copied to each item by default.
If you want that, the header condition amount should not be copied to each item, instead it should be distributed, then in the condition type(V/06) , mark the Header condition as "Group condition ">

Manual Condition Type should be visible in Sales order by default

Hi
How to maintain manual condition types in Sales orders by default. They will be maintaining the value based on the discussion they had with the customer(Negotiated price). The condition type should be visible in the procedure and they will only enter the value.(The method of keying condition type manually is not accepted by the client).
Thanks in advance.
Regards
Vamsi Javaji.

Hi,
In the PRICING PROCEDURE V/08 maintain the CONDITION TYPE as Mandatory
In the CONDITION TYPE V/06 maintain the field MANUAL ENTRIES as C which is Manual entry has a priority.
And check the box VALUE
Now maintain the condition records for the condition type in VK11 with 0 value
Now while processing the sales order the CONDITION TYPE will trigger from the CONDITION RECORDS with 0 value and this can be in EDITABLE mode ( and maintain the value)because of the check box VALUE you flagged in V/06.
Please try this and revert back if you need further details
thanks,
santosh

Pricing condition records should not be picked up

Hi,
I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
Do I have to use any Userexits, if so which one?
Regards,
Abhishek

As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
To configure new Document Pricing Procedure:
IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
Pricing Procedure Determination:
In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Pricing Procedure Configuration:
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka

Expense condition type does not transfer to CO-PA

Dear guru,
My client would like to post expense (ex. promotion expense) via sales order, then SD consultant create condition type and assign expense G/L to this condition type and I assign this condition type to value field via tcode KE4I. When we create sales order and use this condition type, value of this condition type is not transfered to the value field. I set cost element with category '1'. I know standard is not support for this situation. Please kindly to suggest me for solve the problem 'How do expense value of condition type from sales order will be transfered to CO-PA', example user exit or others.
Thanks in advance.
Regards,
Nattakarn.

Hi
Changing the cost element category to 12 can be done only at the begining of the fiscal year as follows
But if promotional expenses is already created as a cost element with say category 1, now if you want too change it you might get an error KS134 Field change CElem Category is not possible (transaction data already exists)
Hence use TCode KA02, Edit->Analysis Period, Click other analysis period provide from begining of fiscal year to 12/31/9999.
You might have to create a new GL Account cost element if you want to go ahead with the changes in middle of the fiscal year
Regards,
Suraj

Condition origin in Header condition type

Dear Experts,
I am on ECC 6.0 and have defined a pricing procedure for PO. I have defined a condition type at the header level ZRB1 for freight.
When i create a PO, it does not allow me enter a freight value at the header. The requirement is , e.g, i enter 100$ as freight at header level which gets distributed as per the grouping condition for the items.
The problem is that header condition type is pointing to the condition origin at the item level. Is there an option to modify the condition origin by selecting the condition type details in the header?
Thanks in advance
Learner

Hi,
In M/06, tick the condition as header and also as group and routine 0.
if you want to distribute this cost to line item apportinoately tick item condition also.
what i see from your you are looking for that, so tick both header and item condition and group condition.
Regards
Rajesh

Header condition types and item condition type

Hello Gurus,
this is a simple question. does the header condition types are totally same as item condition types ?
thanks very much!

hi,
header:
If this condition is marked as a header condition, it is possible to enter the condition type in the header condition screen. Checks for changing the condition manually are unaffected by this.
the header conditions calculate the header value
item : conditions of this type are allowed to be entered in the document items. The condition is then only valid for the particular item in which it is entered.
item condition calculate at item level
(freight condition)for eg = HD00 is a header condition .here if you have 10 materials and this cond type calculates the freight charges for all the 10 items.
KF00 is aitem condition.here system caliculates the freight charges only for that particular items.
Edited by: MANI ROOPA SD/MM on Apr 24, 2008 2:32 PM

Additional VAT condition type is not flowing to PO

Dear All,
            An additional tax of 1 % is levied in State of gujurat and for this we can take the credit . It behaves exactly like VAT like it calculates its value as 1% of base amount and excise duty levied on it . But this condition is not available in standard TAXINN procedure . So we created a new procedure copying from TAXINN .We created a condition type copying from standard condition type JVRD that is for VAT on which we take credit .Then we assign this condition type to tax procedure immediately below condition type JVRD and it should calculate the value in the same way as that of VAT .Then we assigned this procedure to India , assigned all the condition types in CIN config and maintained default condition types for this procedure copying from TAXINN .
            But while we are creating a PO after that ,this additional tax condition type is not flowing in it .
Can anybody let me know where is the missing link in this customisation .
Regards
Abhijit Das

Hi AP ,
         The condition type is Valid from : Todays Date and valid to 31.12.9999 . Is there any problem with this ?
Abhijit

Condition type is not get in the PO output

Hi,
I have defined a new condition type ZRA0- Discount as discount charges .
The condition type is not getting print out in PO copy.
The vendor wants to see in the PO copy.
Pls suggest how to configure
Regards
Sp

Hi,
If i understood your problem, you would like to print the discount in PO print copy along with price.ok.
then check with your Abaper,he can fetch the Discount value for that perticular condition type(ZRA0) & print in the PO copy.Its depends on the print programme to get the data from the document to the print out.
Regds

ZPRS- Cost(data source H) condition type is not visible in CRM sales order

Hi Colleagues,
I created a sales order in ERP. In the sales order the condition type ZPRS- Cost(data source H) is available. I downloaded the this sales order to CRM i can able to see the ZPRS condition type in sales order.
But when i create a new sales order with the same data (BP, Material,Sales organization) the condition ZPRS is not visible in the sales order. When i checked the PRC_TRACE it is showing the error as "Condition with external datasource has not be found".
Can any body help me in this issue.
Tanks and Best Regards,
Rajeswari

Hi Michael ,
Thank you very much for your answer. I just require one more confirmation from you.
Could you please confirm If we post a returns document in CRM system directly the "ZPRS or VPRS - Cost" Condition type will not appear in the return document condition types.
Untill and unless it is a billing document in CRM system the "cost" condtion wont appear rt?
Could you please confirm it.
Thanks in advance for your help.
Best Regards,
Rajeswari

Output type should not be triggered when error in invoice

Dear Experts,
I have this issue.
Whenever there is an error in the document, the output type should NOT be triggered.
But in my case, in spite of the error "Pricing error in item 0001"the output is getting triggered.
This is a Billing Document.VF03.
In NACE, it is linked to RSNASTED-->EDI_PROCESSING form routine.
i need your help in identifying, where should be looking for this check.
check: when error in document->do not post idoc via the output type.
where will i be able to find this check.
Please guide.
Regs,
SuryaD.

FORM KOBEV_907.
*{   INSERT         D94K915917                                        1
* Declaration for Constants
constants : lc_kschl type char4 value 'ZNTP', " Message type
            lc_h type char1 value 'H',        " CREATE TRANS. TYPE
            lc_v type char1 value 'V'.        " CHANGE TRANS. TYPE
IF komkbv3-trtyp EQ lc_h.        " CREATE
IF komt1-kschl <> lc_kschl.
*   Check o/p type ZNTP in the newly proposed o/ps in table NNAST
    READ TABLE nnast WITH KEY kschl = lc_kschl.
    IF sy-subrc EQ 0.
      sy-subrc = 4.
      EXIT.
    ENDIF.
ENDIF.
sy-subrc = 4.
CHECK : KOMKBV3-UVALL CA ' C'.
CHECK : KOMKBV3-UVPRS CA ' C'.
CHECK : KOMKBV3-UVALS CA ' C'.
CHECK : KOMKBV3-RELIK EQ SPACE.
CHECK : KOMKBV3-RFBSK EQ 'C'.
sy-subrc = 0.
ELSEIF komkbv3-trtyp EQ lc_v.    " CHANGE
IF komt1-kschl <> lc_kschl.
* Check o/p type ZNTP in existing o/ps in table xnast and NNAST
    READ TABLE xnast WITH KEY kschl = lc_kschl.
    IF sy-subrc EQ 0.
      sy-subrc = 4.
      EXIT.
    ENDIF.
    READ TABLE nnast WITH KEY kschl = lc_kschl.
    IF sy-subrc EQ 0.
      sy-subrc = 4.
      EXIT.
    ENDIF.
ENDIF.
    sy-subrc = 4.
    CHECK : KOMKBV3-UVALL CA ' C'.
    CHECK : KOMKBV3-UVPRS CA ' C'.
    CHECK : KOMKBV3-UVALS CA ' C'.
    CHECK : KOMKBV3-RELIK EQ SPACE.
    CHECK : KOMKBV3-RFBSK EQ 'C'.
    sy-subrc = 0.
ENDIF.
*}   INSERT
ENDFORM.
the above code is what i see in RV61B907

Condition type is not reflecting in sales orders

hi,
i have created two condition type like jser (service tax) and other one is jste(service tax +cess) but in pricing procedure jfact it is reflecting but while making contract order these two condition type is not accessing.
please help in this connection.

Hi,
After Creating the CONDITION TYPES you need to assign the condition types in the PRICING PROCEDURE
goto the
SPRO->FINANCIALACCOUNTING>FINANCIAL ACCONTING& GLOBAL SETTINGS>TAX ON SALES /PURCHASE>BASIC SETTINGS--->CHECK CALCULATION PROCEDURE.
Here select you procedure and assign the CONDITION TYPE
regards,
santosh

Valuation type is not defined for delivery item 000010 (help me)

hi
when i post goods issue in delivery it is giving error "Valuation type is not defined for delivery item 000010"
even i have assigned material to valuation class and valuation category , but till it is giving error . plz helm out

Hi,
you need to assign proper G/L accounts in OBYC for your plant/gen modification key/valuation class
Go to your material master..check the accounting view.See whats the valuation class.
Now go to OBYC - GBB
here for the combination of your plant & modification key VAX, VAY & VKA & your valuation class give the resepective G/L accounts.
this should solve your problem.
thanks

Header condition type should not be editable at item level

Similar Messages

Maybe you are looking for