cancel
Showing results for 
Search instead for 
Did you mean: 

LSMW for Mass update of PIR with condtions and multiple Scales

Former Member
0 Kudos

Hi ,

I have a requirement of mass creation of Purchase Info Records along with Condition records and multiple Scales using LSMW.

for one purchase info record, i have a condition record with multiple scale records ( Quantity Scales).

TCODE for this is ME11.

I have used the standard Batch Input Program (RM06IBI0) for this and passed 3 source structures with data.

1)  EINA_EINE

2)  KONP and

3) KONM ( Quantity Scales)

in the Field Mapping & conversion rules,

I have mapped the field for below fields.

1) EINA_EINE

     TCODE = 'ME11'

     LIFNR

     MATNR

     EKORG
     WERKS
     LOHNB

     PIPEL

     KONSI

     MATKL

     MEINS

     UMREZ
     UMREN

     EKGRP

     WAERS
     MINBM

     NORBM

     APLFZ

     NETPR

     PEINH

     BSTAE

     BSTMA

2) KONP

     KSCHL

     KBETR ( Condition Amount) --Not mapping this field since i have multiple scales for 1 condtion record.

     KONWA

     KPEIN
     KMEIN

     LIFNR
     DATAB

     DATBI

     STFKZ

3) KONM
    

     KSCHL

     KSTBM

     KBETR


eg: I have one purchase info record to be created with -- 1 Condition record -and  3 scale records  under this condition record

PB00-- valid from 16-12-2013 Valid to 31-12-9999

Scales for this like below:

Quantity                Price

     1                        10

     10                        9

     100                      8

so in EINA_EINE - i am passing 1 record with LIFNR,MATNR,WERKS,EKORG etc

in KONP--> passing 1 record with Condition Type(PB00), LIFNR,DATAB,DATBI etc

in KONM--> passing 3 records each with different quantity and price as above mentioned.

In the read step, it is reading only 1 scale record instead of 3 scale records and in convert step i am able to convert only 1 record.

(means only 1 scale for 1 condtion record)

But i need 3 records to be read and convert so that i can create the PIR with condition record with 3 scale items.

Please suggest me how to get it.

if we cannot use this program, please suggest if there is any other way to create the PIR with condtions and scales.

Thanks in advance

Prem Kumar

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Prem

Were you able to solve this problem?

If yes, please state how?

Former Member
0 Kudos

Hi,

Please define the common fields of all the 3 source structures in the same order in all the 3 source structures and followed by other fields.

eg:

if you are maintaining 3 source structures.

ZEINE

     L

       ZKONP

               L

                ZKONM

Below are the Common field we can define in each source structure and these should be defined in the same order.

ZEINE - Fields:

ZMATNR                         C(020)    Legacy Material #

LIFNR                          C(010)    Vendor #

                               Selection Parameter for "Import/Convert Data"

MATNR                          C(018)    Material #

                               Selection Parameter for "Import/Convert Data"

EKORG                          C(004)    Purchase Org.

WERKS                          C(004)    Plant

ESOKZ                          C(001)    Info record category

ZKONP - fields

LIFNR                          C(010)    Vendor #

MATNR                          C(018)    Material #

EKORG                          C(004)    Purchase Org.

WERKS                          C(004)    Plant

ESOKZ                          C(001)    Info record category

KSCHL                          C(004)    Condition Type

ZKONM - FIelds

LIFNR                          C(010)    Vendor #

MATNR                          C(018)    Material #

EKORG                          C(004)    Purchase Org

WERKS                          C(004)    Plant

ESOKZ                          C(001)    Info record category

KSCHL                          C(004)    Condition Type

Hope this helps.

Former Member
0 Kudos

Hi Prem,

Thanks for the info.

how did you manage to find the solution for this.

An explanation of the below example would suffice.