Variant pricing not working

Hi,
I created a variant material computer - KMAT type.
created characteristics ZCOMPUTER with values monitor, keyboard, mouse, price.
created class - ZTOWER and assigned above characteristic values to this class.
created condition records for computer & variants.
created order and i don't see any price determination.
please help where i am wrong.
thanks

You could base my reply below and use it you create your own variants as per your requirments.
You should create separate characteristics for monitor, keyboard, mouse for example Zmonitor, Zkeyboard, Zmouse and assign values for them.
You should create a separate characteristic for price for example ZPRICE.
Delete characteristic Zcomputer.
Material: computer of KMAT material type.
Charactersics
Zmonitor - values samsung, hp
Zmouse - values wireless, optical
zkeyboard - values microsoft, toshiba
ZPRICE: just enter in Addl tab Table name as SDCOM & Field name as VKOND. System would copy info from data structure maintained in table SDCOM.
Class
ZTOWER and assign the above characteristics to this class.
Now go back to characteristics Zmonitor
select value 'samsung' from TAB values From Menu bar select Extras -> Object dependencies ->.Editor
in line 000010 enter $self.ZPRICE='samsung'
select value 'hp'
in line 000010 enter $self.ZPRICE='hp'
similarly do this for values in characteristic zmouse & zkeyboard.
Now create a pricing condition record PR00 for material computer.
create variant condition record VA00 in condition record VK11 for characteristic values samsung, hp, wireless, optical, microsoft, toshiba.
create sales order and you would get a box to choose variants.
please let me know if it works.

Similar Messages

Layout variant is not working in background in ALV report

Hi,
I have one LAV report to send the report output through mail in foreground and backgroud.Final internal table is having 46 fileds to display the output.But here user is saving the layout variant and sending that layout variant output to mail id in excel format with zip file.Its working in foreground.But in background its not working.Even if we select the layout variant,its sending all the 46 fileds to mail.
here we have used the below FM to update the fieldcat itab.
CALL FUNCTION 'REUSE_ALV_GRID_LAYOUT_INFO_GET'
    IMPORTING
      et_fieldcat   = it_fieldcat[]
      es_variant    = v_disvariant
    EXCEPTIONS
      no_infos      = 1
      program_error = 2
      OTHERS        = 3.
In for ground NO_OUT = 'x' for non selected fields and NO_OUT = ' ' for selected fields.
But in background NO_OUT = ' ' for all the fileds, even if we select the layout variant.
Please suggest me with the solution.
Regards,
Jayaram

hi ,
Do according to this
SORT t_ekbe by belnr.
if t_ekbe[] is not initial .
      SELECT MBLNR
        BWART
        SMBLN
        ERFMG   " This is the new added field
        erfme     " This is the new added field
      INTO CORRESPONDING FIELDS OF TABLE t_mseg
    for all entries in t_ekbe
      from mseg
      where mblnr = t_ekbe-belnr
      AND   bwart = '101'.
endif.
after this
loop at t_ekbe .
loop at t_mseg where mblnr = t_ekbe-belnr .
t_ekbe-ERFMG = t_mseg-ERFMG .
t_ekbe-erfme =   t_mseg-erfme .
modify t_ekbe transporting ERFMG erfme .
clear t_mseg .
endloop.
clear t_ekbe .
endloop.
Regards
Deepak .

Two transaction variant do not working for a user

Hi Gurus
I have created two Z t code and made transaction variant through T Code SHD0 and assigned these two ZTcode to a user. now when a user is running the Ztcode screen variant is active on only one. when i assign second one to the user again than screen variant of first ZT code do not work.
can any one tell me why system is doing so.
Regards
Shiv

Hi, I have the same situation. Can you please help how your case got solved ?
Basically I have created two transaction variants- one for XD02, the other for XD03. When I am trying to assign a user to both these transaction variants ( using SET PROPOSAL), only one is getting assigned, other is getting deactivated. Please help.

'Get Variant' button not working correctly for report

Hi,
I have created an internet service for a custom report. For some reason, when I click the 'Get Variant' button I get a popup, but it does not have any entries to choose from. It is blank. In SE80, the button works correctly. Any ideas?

I figured it out myself. I didn't have the parameter ~webgui set.

CRM 5.0 E-Commerce B2B Internet Sales Pricing Not Working

We have configured a demo of B2B Internet Sales using SAP Best Practices Building Blocks (C14) along with other CRM building blocks. Pricing in CRM through CIC Web client is working properly. In Internet Sales, no pricing appears in the catalog or in the shopping basket. In the shopping basket the message "Pricing Document Could Not Be Created" appears. No additional information appears to be available in the ISA application.
When the order is saved after ignoring the pricing message, it is shown in CRM (CIC) with an error message "Pricing Document Currency Missing". Entering the currency "USD" through CIC causes pricing to appear. So this looks like some type of configuration issue where the ISA application is not finding the currency.
Any ideas would be appreciated.
--Will.

Thanks Srinivas,
Another member on my team found that we needed.
1. The Sales Order Transaction (ISBB) for Internet Sales was configured to use the wrong pricing procedure. It should have been "ISA Coll Show (Bskt)".
2. In the Sold-to business partner, the Sales Area Data needed to have the Sales Organization and Distribution Channel 02 with a blank Division.
CIC uses the same Sales Area data but with a Division specified. This is still somewhat confusing to me.

Pricing Not Working

Hi,
I am working in SAP Warranty Claim Process. We added a new item type. While creating a claim we assign its pricing related
data i.e the amount and currency in a condition type that is assigend to our pricing procedure.
The Item gets created correctly but when i want to manually change the pricing when i am in claim, it does not accept it.
Other item types which fall in same pricing condition type accept the manual change but the new one does not accept it.
We have a discount pricing cond type . So when i change manuallly only for the new item type discount comes for rest other items it doesnt give any discount.
Please advice if i am missing something in configuration.
Thanks for your help.

Hi swati,
We have a discount pricing cond type . So when i change manuallly only for the new item type discount comes for rest other items it doesnt give any discount.
check whether the the dicount condition type is configured what is amintained for Manual entries (OWTYP21), also check whether any Requirment is asgined to it? (OWTYP31)
Also check if this discount condition type is having any kind of restriction?

Carry out new pricing not working in Me23n

Dear Experts,
I am trying to carryout new pricing in purchase order i.e iam going into Item conditions of PO and hit update button on the botton of the conditions tab and select B as the pricing type . The value changes to the new rice and then I save the PO.
After hitting save the values remain unchanged .
Please help on this .

hi,
you sales orders which are already created then you changed the access key. For these order unless you run an update pricing they cannot be updated. Now for the new sales orders which are going to be created if the new key combination matches the sales order criteria then it gets picked up automatically and you dont to do anything.
as we understand from access sequence setup, we do it frm the most specific to the most general ( while setting up the condition tables ie key combinations), So when a condtion record is found whether new key combination or old if its the relevant one and a condition is found for it, it gets picked up automatically.
regards
sadhu kishore

Layout variant not working

Hi ,
I have executed a report . I hide one column and saved the layout. The layout name comes on to the selection screen parameter which i have defined on the selection screen.
PARAMETERS: p_vari LIKE disvariant-variant. " ALV Variant
i have made the i_save = 'A' and is_default = 'x'. and also used other function modules reg. Variants.
but if i select the layout variant in the selection screen and execute it is not working . the hidden column also coming on the output.
But if the select the layout variant on the output of the report from the icon select layout it is working fine. the column which i have hidden is not coming. it is perfect. why it is not working when i select the variant in the selection screen.
Regards,
Rose.

Hi,
Please try this code
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
w_variant-report = sy-repid.
* Function module to show the variant of a ALV report
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = w_variant
      i_save     = 'A'
    IMPORTING
      es_variant = w_kvariant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 2.
    MESSAGE ID sy-msgid TYPE 'S'      NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    p_vari = w_kvariant-variant.
ENDIF.
END-OF-SELECTION.
MOVE w_variant TO w_kvariant.
    MOVE p_vari TO w_kvariant-variant.
    MOVE sy-repid TO w_kvariant-report.
*   Function module to check the variant existence
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
      EXPORTING
        i_save     = w_save
      CHANGING
        cs_variant = w_kvariant.
    w_variant = w_kvariant.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program          = sy-repid
      i_callback_pf_status_set    = 'SET_PF_STATUS'
      i_callback_user_command     = 'USER_COMMAND'
      i_callback_html_top_of_page = 'HTML_HEADING'
      i_grid_title                = text-t06
      i_grid_settings             = wa_grid_set
      is_layout                   = wa_layout
      it_fieldcat                 = t_fieldcat
      i_save                      = 'X'
      is_variant                  = w_variant
      is_print                    = wa_print
    TABLES
      t_outtab                    = t_header
    EXCEPTIONS
      program_error               = 1
      OTHERS                      = 2.
IF sy-subrc <> 0.
    CASE sy-subrc.
      WHEN 1. RAISE program_error.
      WHEN 2. RAISE others.
    ENDCASE.
ENDIF.
Regards
Krishna
Edited by: Krishna Gowrneni on Apr 17, 2009 5:27 PM

Transaction variant not working in quality

Hi,
I have created a transaction varient in SHD0 and activated it in develpoment and then
it is working fine in development system.Then variant transported to quality and there also
it is activated but somehow it is not working in qulaity sytem.
I checked in the respctive transaction with following path
SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
below screen program.
Pl suggest the resolution.
Regards,
Rushikesh

Hi,
Check the variant is transported properly in QA. If present then check the transaction for the same.
If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
Thanks
Subhankar

Screen variant not working when assigned to transaction variant in SHd0

Dear All,
User requires tax code column for line items in MIRO to be made non-editable. I am using SHD0 transaction for the same. I am able to make the column grey-off by creating screen variant. The program is SAPLMR1M and screen number 6310. When tested individually thru SHD0 the variant is working perfect. But it is not working when assigned to a transaction variant. Any clues on the same would be really helpful.
Thanks in advance
Komal

Hi,
Try to record again for the whole set of screens instead of doing that for the individual tax screen and only for the tax screen make the required field disable.
Once done and saved, you can see all the screens variants in the transaction variant.
Use the Change WITH PROCESSING OPTION.
Hope this solves your problem
Regards
Shiva

Transaction variant not working

Hey,
I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
The reconstruction steps are as follows:
SHD0 -
Creation of transaction variant - with processing.
Activating it.
Appreciate a quick response. Thanks in advance.
Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
[email protected]
Regards,
Z

hi,
just check out the following pre-requisites if you have followed them or not:
You can assign various transaction variants to individual sales document types.
With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
Preassigning fields with values
Fading out and changing input availability for fields
Fading out entire screens
In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
Activities
You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
regards,
Siddharth.

Screen Variant Not working

Hi,
I have created one screen variant for screen for SAPLBBP_SC_UI_ITS screen 230.
It's getting called while i checked by debugging .
But its not working in ITS Template & in transaction also .
In SAPgui it's not working .
Is there any more setting for Screen variant apart from just save it & called in screen variant BADI .
Thanks,
SS

Hi
<u>This BADI as you can see by name is for Screen Variants.
BBP_SCREENVARIANT in this case.</u>
<b>Please read the following documentation to get the clear difference</b>
Transaction Variants and Screen Variants
Transaction variants can simplify transaction runs as they allow you to:
Preassign values to fields
Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
Screen variants
Screen variants allow you to simplify screen editing by:
Inserting default values in fields
Hiding and changing the ready for input status of fields
Hiding and changing the attributes of table control columns
A screen variant contains field values and attributes for exactly one screen. A screen variant can, howevever, be assigned to multiple transaction variants. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.
For more information, see: Calling Screen Variants
A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Database Variant to Data.vi not working for the Date datatype with LV 8.2?

I'm moving a large body of LV database code from LV 7.1 to 8.2 and find that the Database Variant to Data.vi is not working correctly when used with the Date datatype. It works fine with 8.0, and the common Variant to Data works also. Am I missing something? Thanks in advance for any assistance. Wes

Thanks for the prompt reply Crystal,
The data is stored in an Oracle database using the DATE type. I'm querying many rows along with other columns and converting each of the values as necessary for each column with the 'Database Variant to Data' vi. Only conversion to Timestamp is no longer working as of version 8.2. I recognize that plain Variant to Data works but I have many (100's) of VIs to change if that is the only solution (not the end of the world). Most often the dates are originally generated in the database using PL/SQL procedures calling SYSDATE which look like: 5/1/2006 11:56:26 AM (in TOAD anyway) which I then need to read into LV as type Timestamp.
Regards, Wes.

Transaction variant to disallow change in FB02 not working for FBL5N / FB09

Hi SAPtechies,
I have created a transaction variant to disallow change in all fields other than Text (BSEG-SGTXT), and activated it for standard transaction FB02.
This works well when FI document is changed via transaction FB02, but fails when the same document is changed via FBL5N / FB09.
The screen is same for FB02 & FBL5N:
Program (screen)     SAPMF05L
Screen number        301
Program (GUI)        SAPMF05L
I have already checked for enhancement in PBO INCLUDE MF05LO00, but there was no success.
Can anyone suggest me another methadology to greyout or make FB02 fields uneditable, with same functionality also working for FBL5N/FB09?

Hi ,
I could achieve a way to disallow editing in FB02 item level fields using substitution & custom exit.
Additional requirement was that I want to assign authorization for particular users who can change all fields.
Any suggestions on it?
Our Basis team has created new role & assigned this role for FB02.
But this role has got many technical authorization objects.
Below check is not working:
AUTHORITY-CHECK OBJECT 'S_TCODE'
           ID 'TCD' FIELD sy-tcode.
Thanks...Tanaya

Condition JEXC not working in Pricing procedure for Non Set Off

Hi,
     While creating PO in case of Dealer procurements i; e we are not buying the materials from the direct manufacturer but from dealer we need to have BED other than 8%(maintained in J1ID).
      I am using the condition type JEXC in the Pricing procedure which is used to overwrite the value of BASIC Excise Duty in   the Tax procedure. For this I have added JEXC in our Pricing procedure with subtotal as "5".
   JEXC value in the Condition tab becomes the value of JMO1/JMO2 in the invoice tab.
Now for Set off cased it is working fine. I used to put value in the JEXC in the condition tab other than actual 8% value and it overwrites the value of BED(JMO1/JMO2) .
But for Non set off cases it not working correctly. It overwrites the value of BED(JMO1/JMO2) correctly but the SECSS % becomes zero. Can anyone suggest me the way I can go for non set off case .

Hi
Kindly have a look: http://help.sap.com/erp2005_ehp_03/helpdata/EN/0e/db7eb4e9114d85a9335fb1df617504/frameset.htm
Regards
Prasanna

Variant pricing not working

Similar Messages

Maybe you are looking for