Info Record Upload

Hi,
We are going for Go Live later this month.I want to have a suggestion regarding the upload of info records.Since client is moving from existing system to SAP for the first time, do we need to have the info recs also created/uploaded first.
I mean how info records will be taken care off.Do we need to have them created before go live or as and when the transactions happen after go live,it will create them.
What should be approach for info records ?
Thx in advance
Regards,
Manoj

Hi Manoj,
Its purely your choice , but uploading the same will say your time and effort .
a few more inputs for the same .
You can transfer the following <b>Purchasing</b> data from your legacy system:
Purchase orders
PO history
PO texts
Purchase requisitions
Purchasing info records
Purchasing data is transferred using the following programs:
Purchasing data      Business object        Program
Purchase orders              (BUS2012)       RM06EEI0
PO history                                             RM06EEI1
PO texts                                                RSTXLITF
Purchase requisitions      (BUS2105)        RM06BBI0
Purchasing info records    (BUS3003)       RM06IBI0
In this step you carry out the pre-processing steps in preparation for a data transfer.
The following steps are necessary:
1. Transfer of master data
A prerequisite for the transfer of purchase orders is that vendor master data, material master data, and purchasing info records already exist in the system.
2. Maintain accounts
Make the appropriate setting to ensure that it is possible to post direct to the GR/IR clearing account. (Open items will be generated on this account as a result of the data transfer.)
3. Define number range
You maintain number ranges in Customizing for Purchasing under Purchase Order -> Maintain Number Ranges.
4. Deactivate statistics update
You deactivate the statistics updating process for Purchasing in Customizing for the Logistics Information System (LIS) under Logistics Data Warehouse -> Updating -> Updating Control.
5. Deactivate purchase order commitments
You deactivate commitments management in Customizing for the Enterprise Structure underAssignment -> Controlling -> Assign Controlling Area to Operating Concern.
6. Deactivate price determination process
Deactivate automatic price determination in Customizing for Purchasing underConditions -> Define Price DeterminationProcess because you specify the net price of the purchase order in the transfer file.
Further information on price determination is available in Customizing for Purchasing under Conditions -> Define Price Determination Process.
7. Deactivate the message determination facility
Deactivate message determination in order that the transferred purchase orders are not re-outputted.
8. Deactivate text transfer
You deactivate text transfer in Customizing for Purchasing under Purchase orders -> Texts for purchase orders -> Define Text Types and Copying Rules for Header Texts and Define Text Types and Copying Rules for Item Texts.
info source :SAP
regards
kp

Similar Messages

  • Purchasing Info Records upload

    Hi, I am uploading purchasing info records using LSMW and the batch input object 0060. But I do not find ESOKZ in the structures to map the Purchasing Info Records Category.
    Also, I have LIFNR in my source structure and also I see it in BEIN0. But the auto field mapping is not working for this field.
    Can you please advise?
    Thank you very much

    hi dear
    first of all record all the fields which you require through shdb including your vendor code and esokz.
    now
    generate a structure for mapping the fields through table maintainence generator option.you can add any number of fields there.
    actully this must include all the fields which are being fetched from the your flat file.
    please revert back if u find problem.
    reward points if it find useful
    regards
    amit singla

  • Mass Info Records uploading

    Hi SAP guru's
    Is there a reliable method for creation of many (2000) Info Records at once? Quick Test works but it can 'break' without notification. Assembling a spreadsheet to import all required data is not a problem.
    Regards
    Teja

    Hi Teja,
    I have personally tried a number of methods in the past. It depends on a
    few things...
    If this is just a one off activity then LSMW all the way I would say. If this is something that will be reused from time to time then it depends if you use supplementary conditions against PB00 and if you want time dependant conditions. If you do then it becomes tricky. We have used a BAPI to do this from a spreadsheet (Create and change) but it was very tricky to get working.
    If you don't use sup conditions then a CATT or an ECATT will do the job just as well.
    and also one third-party programs which make these kind of tasks very easy. For example, check out Winshuttle (http://www.winshuttle.com) for mass creation of SAP data from Excel.
    Hope this helps some thing
    Regards
    Madhu

  • Upload Purchase info Records using LSMW

    Hi,
      Im uploading purchase info records using LSMW - direct method
    Object               0060   Purchasing info rec.
    Method               0000
    Program Name         RM06IBI0
    i need step by step process for this. any one have done this using this program help me out.
    Regards,
    Vimal

    Hello Jürgen
    and thank you!
    One additional question: When I import info records using LSMW, one condition record (PB00) is created automatically. Is it possible to change the validity of that condition record using LSMW, too? Or can I only create new condition records?
    Thanks again
    Alicia

  • Info record Text download and upload

    Hi,
    Can you guys tell me how to download the info record text from one plant (info record text and purchase order text in inforec) and then i need upload the same text in diff plant. Is there a std way of doing this? (i don't think i have seen it) Can you tell me any download / upload code or the tables i can use to download and the procedure to upload.
    Thanks,
    Appreciated your quick reply.
    Suresh

    info record text :
    Table: STXH  and STXL  Text object :EINA    text id:AT and text name :info record no  .
    Use FM : READ_TEXT
    Purchase order text:
    Table:STXH and STXL  Text object: MATERIAL  text id:BEST and text name: material no
    use Function module SAVE_TEXT to upload or use LSMW

  • Purchase Info Record Texts Upload

    Hello all,
    I am using the standard upload program RM06IBI0 for data migration of PIRs. I have a seperate file that has PO texts.
    When I upload the texts I use the structure BRM06I --> BLINES to transport the text.
    However, there seems to be no way of forcing the text to go into the right PIR text. I only have PO texts to upload but no matter what data I place in the BRM06I structure the LSMW always places the text into the Info Record Note text.
    Can anyone help?

    Hi
    I have encountered the same problem with material BOM creation.
    The reason you get this message is probably because you didn't define correctly the identification field in the source structures.
    In step 'Maintain source fields' you should define the first field of every structure as identification field by creating char field of length 1. Then from the tree view of source fields, double click this field (in change mode) and give appropriate value in field 'Identifying Field Content', meaning 1 for header structure, 2 for items structure etc.
    This should fix the problem.
    Best regards

  • Determining Source Structure u0096 for LSMW to upload Purchasing Info records?

    I am trying to use program RM06IBI0 through LSMW to upload Purchasing Info records. While configuring LSMW, how do I determine the source structure? Can anybody please help me with an example?
    Thanks,
    Ketan

    hi dear
    first of all record all the fields which you require through shdb including your vendor code and esokz.
    now
    generate a structure for mapping the fields through table maintainence generator option.you can add any number of fields there.
    actully this must include all the fields which are being fetched from the your flat file.
    please revert back if u find problem.
    reward points if it find useful
    regards
    amit singla

  • Purchasing Info Records data upload

    Hi, I am uploading purchasing info records using LSMW and the batch input object 0060. But I do not find ESOKZ in the structures to map the Purchasing Info Records Category.
    Also, I have LIFNR in my source structure and also I see it in BEIN0. But the auto field mapping is not working for this field.
    Can you please advise?
    Thank you very much

    Hi
    1) Ideally, you shd create different LSMW project for each info record category. You can see a separate field for each category in BEIN0
    2) Not a big issue. Is it not ?
    Best regards
    Ramki

  • Mass upload for info records when price gets changes

    Dear All,
    How to do Mass upload for info records when price gets change.
    Regards,
    Bhargav

    Hi Bhargav,
    Please upload the present price (Map) by  LSMW . When you are doing the transactions  then automatically by selecting option info update price will be updated the  info record in Order Price history
    Regards
    M B Raju

  • Uploading info records by using BDC

    Hi all,
    Does any one having knowledge in uploading info records (ME11) by using BDC.
    Problem arises when going for multiple scales.
    Can any one let me know how proceed this BDC.
    Regards,
    Raj

    Goto transaction SHBD enter a recording name and specify the transaction code.
    Enter the test data and save it , it will actomatically create a bdc program.
    now select that recording name and click create program icon and specify the program name.
    This is the program which was created using transaction SHDB for XD01.
    include bdcrecx1.
    parameters: dataset(132) lower case.
    DO NOT CHANGE - the generated data section - DO NOT CHANGE ***
    If it is nessesary to change the data section use the rules:
    1.) Each definition of a field exists of two lines
    2.) The first line shows exactly the comment
    '* data element: ' followed with the data element
    which describes the field.
    If you don't have a data element use the
    comment without a data element name
    3.) The second line shows the fieldname of the
    structure, the fieldname must consist of
    a fieldname and optional the character '_' and
    three numbers and the field length in brackets
    4.) Each field must be type C.
    Generated data section with specific formatting - DO NOT CHANGE ***
    data: begin of record,
    data element: KUN16
    KUNNR_001(016),
    data element: BUKRS
    BUKRS_002(004),
    data element: VKORG
    VKORG_003(004),
    data element: VTWEG
    VTWEG_004(002),
    data element: SPART
    SPART_005(002),
    data element: KTOKD
    KTOKD_006(004),
    data element: ANRED
    ANRED_007(015),
    data element: NAME1_GP
    NAME1_008(035),
    data element: SORTL
    SORTL_009(010),
    data element: NAME2_GP
    NAME2_010(035),
    data element: STRAS_GP
    STRAS_011(035),
    data element: PFACH
    PFACH_012(010),
    data element: ORT01_GP
    ORT01_013(035),
    data element: PSTLZ
    PSTLZ_014(010),
    data element: ORT02_GP
    ORT02_015(035),
    data element: PFORT_GP
    PFORT_016(035),
    data element: PSTL2
    PSTL2_017(010),
    data element: LAND1_GP
    LAND1_018(003),
    data element: REGIO
    REGIO_019(003),
    data element: SPRAS
    SPRAS_020(002),
    data element: TELX1
    TELX1_021(030),
    data element: TELF1
    TELF1_022(016),
    data element: TELFX
    TELFX_023(031),
    data element: TELF2
    TELF2_024(016),
    data element: TELTX
    TELTX_025(030),
    data element: TELBX
    TELBX_026(015),
    data element: URL
    KNURL_027(132),
    data element: STCD1
    STCD1_028(016),
    data element: STCD2
    STCD2_029(011),
    data element: BBBNR
    BBBNR_030(007),
    data element: BBSNR
    BBSNR_031(005),
    data element: BUBKZ
    BUBKZ_032(001),
    data element: BRSCH
    BRSCH_033(004),
    data element: LZONE
    LZONE_034(010),
    data element: KUKLA
    KUKLA_035(002),
    data element: BRSCH
    BRSCH_036(004),
    data element: UMSA1
    UMSA1_037(020),
    data element: UWAER
    UWAER_038(005),
    data element: UMJAH
    UMJAH_039(004),
    data element: JMZAH
    JMZAH_040(006),
    data element: JMJAH
    JMJAH_041(004),
    data element: BANKS
    BANKS_01_042(003),
    data element: BANKK
    BANKL_01_043(015),
    data element: BANKN
    BANKN_01_044(018),
    data element: ABLAD
    ABLAD_01_045(025),
    data element: KNKAL
    KNFAK_01_046(002),
    data element: CIVVE
    CIVVE_047(001),
    data element: ANRED_AP
    ANRED_01_048(030),
    data element: ANRED_AP
    ANRED_02_049(030),
    data element: NAMEV_VP
    NAMEV_01_050(035),
    data element: NAMEV_VP
    NAMEV_02_051(035),
    data element: NAME1_GP
    NAME1_01_052(035),
    data element: NAME1_GP
    NAME1_02_053(035),
    data element: TELF1
    TELF1_01_054(016),
    data element: TELF1
    TELF1_02_055(016),
    data element: ABTNR_PA
    ABTNR_01_056(004),
    data element: ABTNR_PA
    ABTNR_02_057(004),
    data element: AKONT
    AKONT_058(010),
    data element: DZTERM
    ZTERM_059(004),
    data element: MAHNA
    MAHNA_060(004),
    data element: BZIRK
    BZIRK_061(006),
    data element: AWAHR
    AWAHR_062(003),
    data element: WAERS_V02D
    WAERS_063(005),
    data element: KALKS
    KALKS_064(001),
    data element: LPRIO
    LPRIO_065(002),
    data element: KZAZU_D
    KZAZU_066(001),
    data element: ANTLF
    ANTLF_067(001),
    data element: PERFK
    PERFK_068(002),
    end of record.
    End generated data section ***
    start-of-selection.
    perform open_dataset using dataset.
    perform open_group.
    do.
    read dataset dataset into record.
    if sy-subrc <> 0. exit. endif.
    perform bdc_dynpro using 'SAPMF02D' '0100'.
    perform bdc_field using 'BDC_CURSOR'
    'RF02D-KTOKD'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'RF02D-KUNNR'
    record-KUNNR_001.
    perform bdc_field using 'RF02D-BUKRS'
    record-BUKRS_002.
    perform bdc_field using 'RF02D-VKORG'
    record-VKORG_003.
    perform bdc_field using 'RF02D-VTWEG'
    record-VTWEG_004.
    perform bdc_field using 'RF02D-SPART'
    record-SPART_005.
    perform bdc_field using 'RF02D-KTOKD'
    record-KTOKD_006.
    perform bdc_dynpro using 'SAPMF02D' '0110'.
    perform bdc_field using 'BDC_CURSOR'
    'KNA1-KNURL'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNA1-ANRED'
    record-ANRED_007.
    perform bdc_field using 'KNA1-NAME1'
    record-NAME1_008.
    perform bdc_field using 'KNA1-SORTL'
    record-SORTL_009.
    perform bdc_field using 'KNA1-NAME2'
    record-NAME2_010.
    perform bdc_field using 'KNA1-STRAS'
    record-STRAS_011.
    perform bdc_field using 'KNA1-PFACH'
    record-PFACH_012.
    perform bdc_field using 'KNA1-ORT01'
    record-ORT01_013.
    perform bdc_field using 'KNA1-PSTLZ'
    record-PSTLZ_014.
    perform bdc_field using 'KNA1-ORT02'
    record-ORT02_015.
    perform bdc_field using 'KNA1-PFORT'
    record-PFORT_016.
    perform bdc_field using 'KNA1-PSTL2'
    record-PSTL2_017.
    perform bdc_field using 'KNA1-LAND1'
    record-LAND1_018.
    perform bdc_field using 'KNA1-REGIO'
    record-REGIO_019.
    perform bdc_field using 'KNA1-SPRAS'
    record-SPRAS_020.
    perform bdc_field using 'KNA1-TELX1'
    record-TELX1_021.
    perform bdc_field using 'KNA1-TELF1'
    record-TELF1_022.
    perform bdc_field using 'KNA1-TELFX'
    record-TELFX_023.
    perform bdc_field using 'KNA1-TELF2'
    record-TELF2_024.
    perform bdc_field using 'KNA1-TELTX'
    record-TELTX_025.
    perform bdc_field using 'KNA1-TELBX'
    record-TELBX_026.
    perform bdc_field using 'KNA1-KNURL'
    record-KNURL_027.
    perform bdc_dynpro using 'SAPMF02D' '0120'.
    perform bdc_field using 'BDC_CURSOR'
    'KNA1-LZONE'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNA1-STCD1'
    record-STCD1_028.
    perform bdc_field using 'KNA1-STCD2'
    record-STCD2_029.
    perform bdc_field using 'KNA1-BBBNR'
    record-BBBNR_030.
    perform bdc_field using 'KNA1-BBSNR'
    record-BBSNR_031.
    perform bdc_field using 'KNA1-BUBKZ'
    record-BUBKZ_032.
    perform bdc_field using 'KNA1-BRSCH'
    record-BRSCH_033.
    perform bdc_field using 'KNA1-LZONE'
    record-LZONE_034.
    perform bdc_dynpro using 'SAPMF02D' '0125'.
    perform bdc_field using 'BDC_CURSOR'
    'KNA1-JMJAH'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNA1-KUKLA'
    record-KUKLA_035.
    perform bdc_field using 'KNA1-BRSCH'
    record-BRSCH_036.
    perform bdc_field using 'KNA1-UMSA1'
    record-UMSA1_037.
    perform bdc_field using 'KNA1-UWAER'
    record-UWAER_038.
    perform bdc_field using 'KNA1-UMJAH'
    record-UMJAH_039.
    perform bdc_field using 'KNA1-JMZAH'
    record-JMZAH_040.
    perform bdc_field using 'KNA1-JMJAH'
    record-JMJAH_041.
    perform bdc_dynpro using 'SAPMF02D' '0130'.
    perform bdc_field using 'BDC_CURSOR'
    'KNBK-BANKN(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'KNBK-BANKS(01)'
    record-BANKS_01_042.
    perform bdc_field using 'KNBK-BANKL(01)'
    record-BANKL_01_043.
    perform bdc_field using 'KNBK-BANKN(01)'
    record-BANKN_01_044.
    perform bdc_dynpro using 'SAPMF02D' '0130'.
    perform bdc_field using 'BDC_CURSOR'
    'KNBK-BANKS(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_dynpro using 'SAPMF02D' '0340'.
    perform bdc_field using 'BDC_CURSOR'
    'KNVA-KNFAK(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'KNVA-ABLAD(01)'
    record-ABLAD_01_045.
    perform bdc_field using 'KNVA-KNFAK(01)'
    record-KNFAK_01_046.
    perform bdc_dynpro using 'SAPMF02D' '0340'.
    perform bdc_field using 'BDC_CURSOR'
    'RF02D-KUNNR'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_dynpro using 'SAPMF02D' '0370'.
    perform bdc_field using 'BDC_CURSOR'
    'KNA1-CIVVE'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'KNA1-CIVVE'
    record-CIVVE_047.
    perform bdc_dynpro using 'SAPMF02D' '0360'.
    perform bdc_field using 'BDC_CURSOR'
    'KNVK-ABTNR(02)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'KNVK-ANRED(01)'
    record-ANRED_01_048.
    perform bdc_field using 'KNVK-ANRED(02)'
    record-ANRED_02_049.
    perform bdc_field using 'KNVK-NAMEV(01)'
    record-NAMEV_01_050.
    perform bdc_field using 'KNVK-NAMEV(02)'
    record-NAMEV_02_051.
    perform bdc_field using 'KNVK-NAME1(01)'
    record-NAME1_01_052.
    perform bdc_field using 'KNVK-NAME1(02)'
    record-NAME1_02_053.
    perform bdc_field using 'KNVK-TELF1(01)'
    record-TELF1_01_054.
    perform bdc_field using 'KNVK-TELF1(02)'
    record-TELF1_02_055.
    perform bdc_field using 'KNVK-ABTNR(01)'
    record-ABTNR_01_056.
    perform bdc_field using 'KNVK-ABTNR(02)'
    record-ABTNR_02_057.
    perform bdc_dynpro using 'SAPMF02D' '0360'.
    perform bdc_field using 'BDC_CURSOR'
    'KNVK-NAMEV(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_dynpro using 'SAPMF02D' '0210'.
    perform bdc_field using 'BDC_CURSOR'
    'KNB1-AKONT'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNB1-AKONT'
    record-AKONT_058.
    perform bdc_dynpro using 'SAPMF02D' '0215'.
    perform bdc_field using 'BDC_CURSOR'
    'KNB1-ZTERM'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNB1-ZTERM'
    record-ZTERM_059.
    perform bdc_dynpro using 'SAPMF02D' '0220'.
    perform bdc_field using 'BDC_CURSOR'
    'KNB5-MAHNA'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNB5-MAHNA'
    record-MAHNA_060.
    perform bdc_dynpro using 'SAPMF02D' '0230'.
    perform bdc_field using 'BDC_CURSOR'
    'KNB1-VRSNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_dynpro using 'SAPMF02D' '0310'.
    perform bdc_field using 'BDC_CURSOR'
    'KNVV-WAERS'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNVV-BZIRK'
    record-BZIRK_061.
    perform bdc_field using 'KNVV-AWAHR'
    record-AWAHR_062.
    perform bdc_field using 'KNVV-WAERS'
    record-WAERS_063.
    perform bdc_field using 'KNVV-KALKS'
    record-KALKS_064.
    perform bdc_dynpro using 'SAPMF02D' '0315'.
    perform bdc_field using 'BDC_CURSOR'
    'KNVV-LPRIO'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNVV-LPRIO'
    record-LPRIO_065.
    perform bdc_field using 'KNVV-KZAZU'
    record-KZAZU_066.
    perform bdc_field using 'KNVV-ANTLF'
    record-ANTLF_067.
    perform bdc_dynpro using 'SAPMF02D' '0320'.
    perform bdc_field using 'BDC_CURSOR'
    'KNVV-PERFK'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'KNVV-PERFK'
    record-PERFK_068.
    perform bdc_dynpro using 'SAPMF02D' '1350'.
    perform bdc_field using 'BDC_CURSOR'
    'RF02D-KUNNR'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_dynpro using 'SAPMF02D' '0324'.
    perform bdc_field using 'BDC_CURSOR'
    'KNVP-PARVW(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_transaction using 'XD01'.
    enddo.
    perform close_group.
    perform close_dataset using dataset.
    Reward if found helpful....
    Cheers,
    Chandra Sekhar.

  • LSMW FOR UPLOADING INFO RECORD-ME11 USING RECODING METHOD

    Hi Guys,
    I am uploading inforecords using LSMW recording method.
    While recording I entered net price and other things properly.
    When I am running the lsmw, net price filed becoming gray(Non editable) filed and system shows error as "it is not an input filed". But if i try to execute the t-code sepeartely this filed is in editable mode.
    Please let me know what is the priblem.
    Thanks
    Dhanu

    Hi Dhanu,
    there is the easiest method to do that you can follow the Direct input method the object for info record id 0060 and program is RM06IBI0,
    With this method you will not get any problems. it is SAP recommended method.
    Bhima

  • When using ZCMMRR08 upload transaction it appears the Info-record may over

    "When using ZCMMRR08 upload transaction it appears the Info-record may over-ride the input data creating a pricing error."
    we have customize this transaction "ZCMMRR08" for contracting and price is suppose to update once a year,i am getting wrong price updated in contract display,any suggestions are welcome

    hi
    Refer the following link.
    http://209.85.173.104/search?q=cache:1nrU3_g6gdoJ:www.le.ac.uk/its/help/sap/mm46b_16.docInforecordHowtocreateME11%2Bsap&hl=en&ct=clnk&cd=6&gl=in
    Reward if helpful.
    Jagadish.

  • BAPI or IDOC to upload quality info record transaction QI01

    Hi,
    If any one knows any BAPI or IDOC to upload quality info record do let me know.
    regards
    Ranveer

    Hi,
    Have you tried doing this in ECATT??
    See this Link:
    http://help.sap.com/bestpractices/BBLibrary/Documentation/G09_BB_InstallGuide_EN_DE.doc

  • Uploading Purchase Info Record

    Hi Experts,
    Can any one advice me what is the best method in BDC has to be used for the conversion of Purchase Info records.
    Do we have a direct method, if yes Please help me out with the program name.
    Thanks in Advance

    Hi in LSMW
    Go for
    Object 0060 Purchasing info rec.
    Method 0000
    Program Name RM06IBI0
    Program Type B Batch Input

  • Mass Creation of Material Group Purchase info record

    Dear All
    Currently we are developing a custom transaction in SAP to mass upload Purchase Info records from a flat file (excel)
    We are using the standard Function Module ME_POST_INFORECORD to create the PIR s
    We use two different number ranges for Material and Material Group PIR s. This is set up already in SPRO>MM>PIR>Define Number Ranges
    Purchasing info record for stock material (Group - IL ) have a number range X
    Purchasing info record for material group (non-stock mat.)(Grpup -IN) have number range Y
    So when we create a Material PIR manually in SAP it picks X number range and  Y number range for Material Group PIR
    But when we create Material Groups PIR via the new custom transaction it creates PIR s with Number range X.
    Upon checking understood that the standard FM ME_POST_INFORECORD is always defaulting the Number Range Group as IL internally . Seems like a harcoding done by SAP
    Wanted to know
    - Is there any another FM we should consider while creating Material Group PIR s. Any other Function module provided by SAP for that ?
    - Or what can be other way to resolve this ?
    Please let me know your views on this.
    Regards
    Shyam

    Hi,
    For mass upload from flat files you can consider LSMW with different options e.g. IDoc:
    Message Type         INFREC
    Basic Type           INFRECMASS01
    or simply via recording of transaction (this should be using exactly the same NR as you have when doing this manually).
    Regards,
    Tomek

Maybe you are looking for