LSMW Pricing Conditions Conversion

Hello.
We are trying to import a large number of pricing conditions. However, the program LSMW uses limits us to about 7 conditions. This, apparently, is because the screen size it is using is small (I have run it in the foreground and seen this). There is a note about this from several years ago, but that should have been addressed in the version we're using.
Questions:
1. Is there a way around this?
2. My friendly Basis people say I will have to modify the program. Has anyone done this?
3. Have I posted this to the correct forum? If not, kindly point me in the right direction.
Thank you.
-Bob Gordon

Hi Bob,
It did work for me, I just tested it.
See below
my header data file1:
PRICE_HEADER FILE STRUCTURE FOR PRICE HEADER.
KOTABNR C(003) condition table
KSCHL C(004) condition type
VAKEY C(100) Variable key
DATBI C(008) Validity end date
DATAB C(008) validity start date
KBETR C(015) Amount field
KONWA C(005) unit/currency Rate
KPEIN C(005) pricing unit
KMEIN C(003) Unit of measuremen
File content
503ZP010032013660000238-005 200612312006013150 USD 1 EA ( One single line in fixed length format)
SCALE structure
KOTABNR C(003) condition table
KSCHL C(004) condition type
VAKEY C(100) Variable key
KSTBM C(015) Scale quantity
KONMS C(003) Scale unit of meas.
KBETR_S C(018) Condition rate
File content
503ZP010032013660000238-005 1 EA 50
503ZP010032013660000238-005 2 EA 49
503ZP010032013660000238-005 3 EA 48
503ZP010032013660000238-005 4 EA 47
503ZP010032013660000238-005 5 EA 46
503ZP010032013660000238-005 6 EA 45
503ZP010032013660000238-005 7 EA 44
503ZP010032013660000238-005 8 EA 43
503ZP010032013660000238-005 9 EA 42
503ZP010032013660000238-005 10 EA 41
503ZP010032013660000238-005 11 EA 40
503ZP010032013660000238-005 12 EA 39
503ZP010032013660000238-005 13 EA 38
503ZP010032013660000238-005 14 EA 37
503ZP010032013660000238-005 15 EA 36
503ZP010032013660000238-005 16 EA 35
503ZP010032013660000238-005 17 EA 34
503ZP010032013660000238-005 18 EA 33
503ZP010032013660000238-005 19 EA 32
503ZP010032013660000238-005 20 EA 31
(Format the data to the fixed lenth per the above structures)
Change that condition type, condition table and the material number per ur requirement.
when you execute the step for create the session select like below.
Max no records per transaction 1
Max. no. cond. recs per screen 1
Max no. scales per screen 7
Max. no. cond. recs in table 500
Let me know if you still have an issue, you may also reach me at [email protected] for any queries.
Thanks,
Prabhu.

Similar Messages

LSMW Pricing Condition changes

Hi,
I need to create a LSMW to change pricing condiitons in condition type PR00 for access sequence table 006 (Price List Type/Currency/Material). I did the following:
1. Defined Object attributes Standard/Batch Direct Input 0070 (Condition record) Program Name RV14BTCI and Program type B (Batch). Method is 000.
2. Where do I define that the new records have to go into this table 006? Will it be in the source structures? Source fields? Can anyone explain me step by step how this will work? And what will be the subsequent steps? The documentation I have on LSMW isn't much help unfortunately and is very generic. I need specific solution/steps to this pricing condition table. Any guidance on it?
Thanks a lot.

Hi Kevin
Pl. check this link on LSMW pricing :
<a href="http://sap-img.com/sap-data-migration.htm">LSMW</a>
<a href="http://sap-img.com/sd001.htm">to upload pricing conditions</a>
Pl reward if it helps.
Thanks & Regards
Sadhu Kishore

PR to PO conversion should not happen in case of expired pricing condition in Info Record

Hi All,
Issue – PR to PO conversion should not happen in case of expired pricing condition in Info Record.
In case of creation of PR/ PO, the Price is pulled out from the Info Record of the material. In our case if the Price in the Info Record is expired, it should give the Error Message & should pick the Price from the last PO created for the same combination of Plant, Vendor, Company code.
Request you to please let us know if there is any way out.
Regards,
Karthick.V

Hi,
As per your requirement if info record price is not valid and in auto PO creation from PR, price should get picked from last PO, this is standard behavior and it will happen.
If you check in customization MM - Purchasing - Environment Data - Define Default Values for Buyers -Settings for default values
Default values if you check under price adoption , it has to be Always copy ( copying of conditions from last PO) . Pls check

How to migrate pricing condition data using lsmw

Hello All,
can any one explain how to migrate pricing condition data using lsmw.
the scenario is we are trying to extend the pricing conditions from one sales area to other sales area on a combination of sales organization, distribution channel and division.

Hi Sreedhar Kodali
Pricing conditions can be extended with the following options:-
1) Customer / material with release status
2) Sales Org / Dist. Channel / Cust group / Material
3) Price List category / Currency / material with release status
4) Material with release status
Assuming that your pricing condition in one sales area is different to another, first you have to create LSMW recording to extend the sales area and then pricing conditions can be uploaded accordingly.
Thanks
G. Lakshmipathi

Recording for a LSMW: item pricing conditions

Hi Experts,
I need your help! I am trying to do a recording for modifying sales orders conditions (for items): VA02, item 10, GO TO PRICING CONDITION ZXXX, change value to Z, go to item 20, GO TO PRICING CONDITION ZXXX, change value to Z,....
My question is: how do I indicate the recording itself that a certain pricing condition has to be modified. Do not forget we are talking about items and the cursor will be in a different place in every item.
Good ideas will be rewarded, that´s obvious.
Regards,
F

Thanks Chandra. The FM you suggested worked fine for my problem / Regards Thomas

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 Mitra

Hi,
Kindly do the pricing analysis and check whether you have the following error such as
Inactive condition type because of subsequent price,
Regards,
Ravi

How to copy the Pricing conditions from one Distribution Channel to another

Generally we use VK11 transaction to create conditional records .
but I Need to Know whether is it Possible to copy the Pricing conditions from one Distribution Channel to another with same name and same internal Characteristics .
Since we have around 70+ of Condition type with different parameter Sequence.So Instead of Going for BDC whether is there any standard Funct Modules/programs/BAPIs to do this?
How to make a copy Condition types from One Distribution Channel to another.
since SAP has already provided to copy conditions from Customer to customer.
Likewise i need to know whether SAP is facilitating for these feature also.
Iam Dubious in this issue.
Hope Fully looking for the answers.
Harish.N

- IDOC_INPUT_COND_A (you can create IDOC, but also call directly)
- call transaction / batch input (use transaction XK15, as used by LSMW)
- use group of function modules RV_CONDITION_COPY, RV_CONDITION_SAVE, RV_CONDITION_RESET + commit.
if you search SDN on 'RV_CONDITION_COPY' you'll find more info I believe.
Someone mentioned BAPI_PRICE_CONDITIONS as well.

Pricing Condition for Serivce Line Item

Hi Experts,
I'm trying to create a service PO with 1 Service line item and this service line item actually contains more than 1 service number. Using BAPI_PO_CREATE1, how can I define the pricing condition for each of the service number?
Currently, I'm able to define the pricing condition of the service item as a whole through this input parameter table POCOND.
Thanks.
Best Regards,
Weishan

Its really tricky requirement, when you are going for manual condition type.
- the best alternative to cater your requirement is to go for maintenance of condition record, which you can upload at mass with the help of LSMW. Also, will be really helpful in having report for pricing. Finally, reduce time to create sales order. Thus, discuss & encourage your user to maintain pricing based condition record. Only header condition should be on manual bases.
- If hard to convince your client on condition record. Then develop a routine with the help of ABAPer in your team. Where you can put logic. If the condition is manual enter and system is able find already entered value for material, then copy the price the slots where system don't find manually entered condition value.
Regards
JP

Pricing Condition during upgrade

Hi,
During our SAP upgrade we are experiencing an issue related to PO pricing conditions. How can we bring over PO pricing conditions in open POs from 4.7 system to 6.0. We are using several custom condition types.
If anybody have an experience like this please share with me for resolving this issue.
Thanks
John K. T.

Hi John,
check the following steps:
1. maintain Z-table for Conversion from old and new conditions
2. Include this table in extraction program (ABAPer'll do this)3.
3. Check the extracted data for accuracy
Now your file is ready with new conditions and new data as per your ECC6 system
4. Then upload this flat file by uploading program.
Revert where you are facing issues? What process you are following?
Umakanth R

Uploading of vk11 (pricing condition) transaction

Hi friends,
I have to upload data from legacy system to SAP using VK11 tcode , can use LSMW for VK11 transaction ? . I have to use batch input standard program....
when we open VK11 tranaction first its asking for condition type ( KSCHL ) for each condition type the next screen is varying .
is it possible to do using recording.?
otherwise
is there any stanadard LSMW program for this ,in the batch input.
what is that program how to use that program.
can any body help me in this regard.
Regards,
Jayan

Hi,
For pricing conditions you will be having the condition type and table name in the
first screen of the VK11 transaction.
In the second screen of VK11 you can see the fields will be varing based up on the
table name you are specifying the first screen.
You can use field VAKEY in the batch input program to pass all the values.
For example:
Your table name A601 contians three fields mentioned below.Leave the fields such as
KAPPL,KSCHL,DATBI,DATAB,KBSTAT,KNUMH since these will be avialble for all the tables.
the rest varing fields are
VKORG     VKORG     CHAR     4
VTWEG     VTWEG     CHAR     2
SPART     SPART     CHAR     2
KUNNR     KUNNR_V     CHAR     10
KONDA     KONDA_V     CHAR     2
MATNR     MATNR     CHAR     18
KFRST     KFRST     CHAR     1
You need to pass the value of all the fields to the VAKEY in the batch input program.
using offset option mentioned below.
VAKEY+0(4) = source-vkorg.
VAKEY+4(2) = source-vkorg.
VAKEY+6(2) = source-vkorg.
VAKEY+8(10) = source-vkorg.
VAKEY+18(18) = source-vkorg.
VAKEY+ 36(1) = source-vkorg.
Hope this will help you

Deletion of bulk pricing condition records

Hello thr,
I have thousands of pricing condition records to be deleted. I use condition type ZP01 in VK12 and select the key combination customer/material and then enter the details and then mark the condition record for deletion. To delete the next condition record, I need to go back and do the entire process again. Could someone please let me know if there is a txn that can help me do this in one step.
Thanks very much for your help.

Hi Swetha,
If you want to delete all conditions for ZP01 condition type, you need to create a LSMW batch input from LSMW t-code. you can check and try followings:
[https://wiki.sdn.sap.com/wiki/display/ABAP/LSMW%20steps%20-Batch%20Input%20Recording]
[http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc]
You should go to in LSMW t-code, a recording should be created for one record from VK12 t-code and it can be run for all records like same from SM35 t-code.
Please follow the links above for VK12 condition deletion.
I hope these will meet your requirement fully.
Regards,

CRMXIF_ORDER_SAVE_M02 - how to populate pricing conditions at header lvl?

Hi all,
im using lsmw idoc basic type CRMXIF_ORDER_SAVE_M02 to create Service Orders.
my problem now is, it only contains pricing conditions segment (E101CRMXIF_PRCD_COND_XT) under the item level.
is there anyway so that i can populate the pricing conditions at the header level?
Many thanks.

Hi Michael,
Thanks alot for the answer.
I had given 6 point for that.
I have couple of more question here.
As you said
bdoc structure can be enhanced using the EEWB or manually, but then you'll have to create the mapping from the bdoc to the CRM DB as well.
My question is what needs to be done to map bdoc to CRM database.
Second thing is
As you said
A new idoctype, including the enhancements done to the bdoc and all mapping functions for inbound and outbound communication, can be generated using transaction BDFG.
My question is what do you mean by New IDoc Type, Do i need to define new idoc type/message type for this enhancement, and the field which i have to add in BDOC structure how it is going to reflect into the corresponding basic idoc. In my case crmxif_order_save_m02, Don't i need to add the same field here in Basic Idoc type.
Please explain me this doubts.
Thanks Alot.
Regards,
Manoj Tiwari

Data migration for pricing conditions

Hello gurus,
I want to migrate my pricing condition data from one sap system to another. I am thinking of doing it using ALE or LSMW. Please tell me which would be the better option and also describe step wise how to do that.
Many thanks.

any items can be transferred.

Bulk Pricing condition record upload

can any body help out for , Is there any transaction code for uploading the pricing condition record in BUlk.
Ex: 1000 condition records upload for condition type PR00..
Ragards

Dear Ramesh,
This you can do by creating an LSMW,one of the mass upload tool.
Regards,
AKD
Edited by: Ashish Dikshit on Sep 19, 2009 9:31 AM

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

LSMW Pricing Conditions Conversion

Similar Messages

Maybe you are looking for