Creating Purchasing info records using transaction ME11

Hello Friends,
I am trying to post Purchase info records through ME11.
Everything is fine but we are not able to record the Conditions tab - i.e, Condition Qty & scale Quantities,
Can anybody Please help is there any BAPI or any Function module to Post Purchase Info records,
i.e, alternative to ME11 transaction.
Thanks in advance,
Regards,
Phaneendra

Hello Rahul,
Thanks for your reply, Here i am using the same.
But i am not able to update data by konp & konm structures.
Do you have any idea on this ?
ie, in flat file only one line is read by the Program for KONM Structure .Please help.
Regards,
Phaneendra
Edited by: phaneendra punukollu on Feb 8, 2010 4:36 PM

Similar Messages

Create Purchase info record using LSMW idoc method

Hello Friends,
I am trying to update Purchase Info records using LSMW Standard program RM06IBI0.
But it is not updating the condition price details and scale Quantity.
For that the form suggessted LSMW IDOC method. with : Message Type         COND_A / COND_A02.
But i dont know is the info record created earlier to this step or else we can create both using this method
at a time ? Does anybody please suggest.
( Actually Purchase Info record created using transaction ME11 ).
Regards,
Phaneendra

you first create the info record and subsequently you load the conditions.
become familiar with the condition tables and its key first. Check How table A017 and A018 are maintained.
Intresting is the field VAKEY which is actually the link to your info record.
This is a combination of vendor, material, purchasing org, plant , and info record indicator.
data: begin of ZZVARKEYA,
        ZLIFNR like LFM1-LIFNR,
        ZMATNR like MARc-MATNR,
        ZEKORG like LFM1-EKORG,
        ZWERKS like MARC-WERKS,
        ZINFTYP like EINE-ESOKZ,
        end of zzvarkeyA.

IDoc status 51 - LSMW for Creating Purchasing Info Records using IDoc meth

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

U should use basic type INFREC01 instead of NFRECMASS01.
Within the FM there is a check for basic type like:
check idoc type
    if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
      raise wrong_function_called.
    endif.
Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM

Error occured while creating purchase info record in mm

sir,
while creating purchase info record an error occured while inserting net price. it said
NOT POSSIBLE TO DETERMINE A CONDITION TYPE FOR A PRICE
when it attempted to generate the time dependent condition for the price you entered the systeem was unable to determine a condition type, price determination is therefore not possible.
please inform me how to solve this problem.
thankyou

I think you are not using the stdard pricing becuse of that it is thrwing error
Ok First check your pricing procedure which your using for PO
than in that pricing procedure if you are using PB00 fro Gross price than you will have antoher pricing procedure attached to this condition.
check in M/06 for your gross price conditon
now did you assign the pricing procedure to vendor?
bottom line is somthing missing in your config.
Check all the config as below
Pricing Procedure:
In MM module, pricing procedure is used during RFQ and PO creation. Total value of material based on all addition and subtraction like discount, surcharge, tax, freight, etc. In this we are defining pricing procedure and linking to vendor and purchase department through the virtual schemas.
Following steps for pricing procedure as,
1. Define conditions.
2. Define pricing procedure.
3. Define virtual purchase organization and vendor.
4. Info Record.
Customization for Pricing Procedure :
1. Definition of Conditions :
/NMEK0-condition typeu2026condition types- definition (define for basic price, net price, discount, surcharge, tax etc.)
2. Defining pricing procedure :
/NMEK0- calculation schema-calculation schemasu2014New entries (Define procedure and put the conditions like formula so that final price will be net price / total value as per company requirement)
3. Linking pricing procedure to independent condition types.
/NMEK0-condition typeu2026condition types- definition for position for defined conditions (Enter the defined pricing procedure in the each independent conditions u201CPricing Procedureu201D box)
4. Defining Schema group for Vendor :
/NMEK0- calculation schema-schema groupsu2014vendoru2014New Entries.
5. Defining Schema group for Purchase Organization--- New entries.
/NMEK0- calculation schema- schema groups---- purchasing organization--- new entries.
6. Linking Virtual Purchase Organization to actual Purchase Organization.
/NMEK0- calculation schema- schema groups----- Assign P.Org. (in actual P.Org, enter virtual P.Org)
7. Linking Pricing procedure to virtual P.Org and virtual vendor :
/NMEK0- calculation schema- Determine Schema--- -Standard --- New entries (Enter virtual schema and P.Org. along with pricing procedure)
8. Linking virtual vendor to actual vendor-- /NXK02 then enter schema group vendor in Purchasing Data )
9. Info Records (/NME11)---- click on u201CPurch. Org. data1u201D and enter condition types and pricing procedure
What are the steps in pricing determination in MM? Condition, Access sequence and schema.
In the SAP MM Pricing is more important. Just yesterday I have completed the Pricing as I am doing the SAPMM now. I can give some light on this Topic, not 100%. After 2 days definitely some more I can share.
The Basic thing is Condition Technique. In which there are
1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table.
A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a Condition Technique.This is a simple logic
Here the Condition Type is very important like PB00, PBXX,RA01 etc.
In the background every Condition Type has its own defition means the purpose of the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions.
Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement.
The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement.
The Pricing Schema means the calculations procedure of Condition Type.
Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means
RA01 is based on PB00 like that we have to define in the Pricing Schema
which makes easy to use in realtime.
Here PB00 has the Access Sequence - 0002.
But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types.
In the system, by default some standard Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define.
For the configuration, I may not able to explain properly through here but will give some Idea.
Configuration: SPRO-IMG-Material Management- Purchasing- Conditions-Define Price Deternmination Process
1. Define Access Sequence
2. Define Condition Type
3. Defince Calculation Schema:- Here you have to define the Schema
Define Schema group
1. Define Schema Group vendor
2. Define Pricing Schema group
3. Schema group for Purchase Organisation
4. Assign Schema group to Purchase Organisation
Define Schema determination
1.define calculation schema for Standard purchase organisation
After completion of the Schema Group, we have to assign it to Vendors.
Then whenever we use any transaction with this Vendor, the concerned Schema will work as configured by us.
I think this will help you. Actually the Pricing is a vast. Becuase each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above.
Here we can create many Calculation Schemas which can assign one schema to Local vendors
another schema to out side vendor one more schema to foreign vendors like that we can classify.

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

FM or BAPI for creating purchase info records and purchase conditions

Hi all,
i need create purchase info records and purchase conditions from txt-file,
What FM or BAPI i can used for this?
Thanks and Regards,
Andrei

You can use trasaction SXDA_TOOLS.....
object type BUS3003
program type BINP
program/method RM06IBI0
but the fields must be sequentially written in the txt, with every space inclusive....

Pricing not updated in Purchase Info Record using INFREC01. is it possible?

Hi Gurus,
I am using IDoc INFREC01 to create Purchase info record for material, but when I see in ME13 that PIR is created successfully but price is never updated, though I have populated field NETPR and EFFPR hence condition PB00 (basic pricing condition) not created.
Is it possible to update only single pricing (basic price PB00) condition through INFREC01 ??? or should I use another BAPI or some standard report ...??.
I am extending Pricing Conditions for Purchase inforec through seprate IDOC: COND_A01, but it could only do that if there is basic pricing condition i.e. PB00.
Please advice.
Thanks in advance.
Robin

HI,
You can update pricing field for conditon type PB00, please use correct validity period.
Even there are no basic Price condition PB00, you can add new condition types with existing types.
Price vaue can depend on the pricing conditions that you have maintained.
Thanks....

Error in Creating Purchasing Info Record

Hi all,
I started practicing MM module recently.In the process i created plant,purchasing org., storage location, material,vendor and then i tried to create purchasing info record.In that it is asking to give plnd delay time.When i entered any number it is giving an error to enter valid field.
Can any one help me in this issue.............
And also can anyone guide me in practicing MM module.
Thanks in advance,
Sunny

Hi
Actually if you maintain the nos. in days in that planned delivery time field, system should not give an error message. I feel the error message could be of different.
Alternatively the avoid the error message or instead of maintained the value of planned delivery time of the material in inforecord, you can maintain it in material master itself in the field "Plnd Delivery Time" under MRP 2 view.
Reward points if its useful.
Best Regards

Creating Conditions for Purchase Info Records using IDoc COND_A01

Hi All,
we are using IDOC COND_A01 to update and add conditions in ME12 transactions.
But when we send a condition IDoc which contains 2 condition types (Segment KONP), the standard function call creates only one database entry in the table KONP. The entry in KONP is for standard condition types PB00, but not for company specific types (Say: ZABC) .But when we create them manually in ME12 maintaining an purchase info record we get both the entries in the KONP database table.
Has anyone come accross such a problem? Is there any special field in the IDoc COND_A01 which controls the creation of the condition types?
Thanks for any answer!

U should use basic type INFREC01 instead of NFRECMASS01.
Within the FM there is a check for basic type like:
check idoc type
    if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
      raise wrong_function_called.
    endif.
Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM

Creation of purchase info records using me11 and me12

are there any bapis for creation / update of purchase info records with pricing conditions using transaction me11 and me12 ?
plz tell me ?
Moderator message: please search for available information before asking.
locked by: Thomas Zloch on Aug 10, 2010 2:52 PM

looks like it accepted A017.
Why did you choose basis type COND_A04 ?
As this one is very special for long material numbers ( more than 18 digit material numbers) do you have such?
E1VFSCAH is the Scale header in case of dimension specific scales. do you have such?
Just try it with COND_A01

Creating Purchase Info Record in SAP using JCO

I am trying to create a Purchase Info Record (ME11) in SAP using the below JCo code:
It executes without fail and throws no error, but i am not able to get the newly created info record in SAP. In ME13 it says info record not found. Can i know what am i missing?
I am using these FMs :
1. ME_INITIALIZE_INFORECORD
2. ME_DIRECT_INPUT_INFORECORD
3. ME_POST_INFORECORD
IFunctionTemplate ft1 = mRepository.getFunctionTemplate("ME_INITIALIZE_INFORECORD");
    JCO.Function function1 = ft1.getFunction();
    mConnection.execute(function1);
    IFunctionTemplate ft = mRepository.getFunctionTemplate("ME_DIRECT_INPUT_INFORECORD");
    JCO.Function function = ft.getFunction();
    JCO.ParameterList importparams =function.getImportParameterList();
    // Setting HeadData Structure Information
    JCO.Structure headStructure = importparams.getStructure("I_EINA");
    //headStructure.setValue("105","MANDT");
    //headStructure.setValue("5300259768", "INFNR");
    headStructure.setValue("MYPART0006", "MATNR");
    //headStructure.setValue("MYPART0006", "IDNLF");
    headStructure.setValue("100002","LIFNR");
    headStructure.setValue("10000","MATKL");
    headStructure.setValue("KGS","MEINS");
    headStructure.setValue("1","UMREZ");
    headStructure.setValue("1","UMREN");
    headStructure.setValue("SG","URZLA");
    headStructure.setValue("KGS","LMEIN");
    //headStructure.setValue("0000005300259768","URZZT");
    JCO.Structure headStructure1 = importparams.getStructure("O_EINA");
    //headStructure1.setValue("105","MANDT");
    //headStructure1.setValue("5300259768", "INFNR");
    headStructure1.setValue("MYPART0006", "MATNR");
    //headStructure1.setValue("MYPART0006", "IDNLF");
    headStructure1.setValue("100002","LIFNR");
    headStructure1.setValue("10000","MATKL");
    headStructure1.setValue("KGS","MEINS");
    headStructure1.setValue("1","UMREZ");
    headStructure1.setValue("1","UMREN");
    headStructure1.setValue("SG","URZLA");
    headStructure1.setValue("KGS","LMEIN");
    //headStructure1.setValue("0000005300259768","URZZT");
    System.out.println("General Data Set");
    JCO.Structure purchaseDataStructure = importparams.getStructure("I_EINE");
    //purchaseDataStructure.setValue("105","MANDT");
    //purchaseDataStructure.setValue("5300259768", "INFNR");
    purchaseDataStructure.setValue("1000","EKORG");
    purchaseDataStructure.setValue("1000", "WERKS");
    purchaseDataStructure.setValue("003","EKGRP");
    purchaseDataStructure.setValue("USD","WAERS");
    purchaseDataStructure.setValue("3","APLFZ");
    purchaseDataStructure.setValue("1","PEINH");
    purchaseDataStructure.setValue("1","BPUMZ");
    purchaseDataStructure.setValue("1","BPUMN");
    purchaseDataStructure.setValue("1000","EFFPR");
    purchaseDataStructure.setValue("0001","BSTAE");
    purchaseDataStructure.setValue("100000","NETPR");
    purchaseDataStructure.setValue("X","KZABS");
    JCO.Structure purchaseDataStructure1 = importparams.getStructure("O_EINE");
    //purchaseDataStructure1.setValue("105","MANDT");
    //purchaseDataStructure1.setValue("5300259768", "INFNR");
    purchaseDataStructure1.setValue("1000","EKORG");
    purchaseDataStructure1.setValue("1000", "WERKS");
    purchaseDataStructure1.setValue("003","EKGRP");
    purchaseDataStructure1.setValue("USD","WAERS");
    purchaseDataStructure1.setValue("3","APLFZ");
    purchaseDataStructure1.setValue("1","PEINH");
    purchaseDataStructure1.setValue("1","BPUMZ");
    purchaseDataStructure1.setValue("1","BPUMN");
    purchaseDataStructure1.setValue("1000","EFFPR");
    purchaseDataStructure1.setValue("0001","BSTAE");
    purchaseDataStructure1.setValue("100000","NETPR");
    purchaseDataStructure1.setValue("X","KZABS");
    mConnection.execute(function);
    IFunctionTemplate ft2 = mRepository.getFunctionTemplate("ME_POST_INFORECORD");
    JCO.Function function2 = ft2.getFunction();
    JCO.ParameterList importparams2 =function2.getImportParameterList();
    importparams2.setValue("MYPART0006", "I_MATNR");
    importparams2.setValue("MYPART0006", "O_MATNR");
    mConnection.execute(function2);
Edited by: rs_d123 on Dec 17, 2011 10:46 AM
Edited by: rs_d123 on Dec 17, 2011 10:46 AM

If i give this much code then it throws an error
Exception in thread "main" com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Enter Purch. group :
I have already set the purchase group in the code: EKGRP as 003. Dont know why its still asking for purchase group.
            JCO.Repository mRepository;
         mRepository = new JCO.Repository("SAPConnection", mConnection);
         System.out.println(" Repository Created ");
         IFunctionTemplate ft1 = mRepository.getFunctionTemplate("ZME_INITIALIZE_INFORECORD");
         JCO.Function function1 = ft1.getFunction();
         mConnection.execute(function1);
         IFunctionTemplate ft = mRepository.getFunctionTemplate("ZME_DIRECT_INPUT_INFORECORD");
         JCO.Function function = ft.getFunction();
          JCO.ParameterList importparams =function.getImportParameterList();
          // Setting HeadData Structure Information
          JCO.Structure headStructure = importparams.getStructure("I_EINA");
          headStructure.setValue("MYPART0006", "MATNR");
          headStructure.setValue("0000100002","LIFNR");
          headStructure.setValue("000010000","MATKL");
          headStructure.setValue("KGS","MEINS");
          headStructure.setValue("1","UMREZ");
          headStructure.setValue("1","UMREN");
          headStructure.setValue("SG","URZLA");
          headStructure.setValue("KGS","LMEIN");
          System.out.println("General Data Set");
          JCO.Structure purchaseDataStructure = importparams.getStructure("I_EINE");
          purchaseDataStructure.setValue("1000","EKORG");
          purchaseDataStructure.setValue("1000", "WERKS");
          purchaseDataStructure.setValue("003","EKGRP");
          purchaseDataStructure.setValue("USD","WAERS");
          purchaseDataStructure.setValue("1","APLFZ");
          purchaseDataStructure.setValue("1","PEINH");
          purchaseDataStructure.setValue("1","BPUMZ");
          purchaseDataStructure.setValue("1","BPUMN");
          purchaseDataStructure.setValue("1000","EFFPR");
          purchaseDataStructure.setValue("0001","BSTAE");
          purchaseDataStructure.setValue("1000","NETPR");
          purchaseDataStructure.setValue("X","KZABS");
          mConnection.execute(function);
         IFunctionTemplate ft2 = mRepository.getFunctionTemplate("ZME_POST_INFORECORD");
         JCO.Function function2 = ft2.getFunction();
          JCO.ParameterList importparams2 =function2.getImportParameterList();
          importparams2.setValue("MYPART0006", "I_MATNR");
          mConnection.execute(function2);
          System.out.println("Execution Completed");
Edited by: rs_d123 on Dec 19, 2011 9:04 AM

Problem with Purchase Info Record Condition Data ( ME11)

Hi all,
I am trying post Data for Purchase Info Records with Conditions data.
I am using a standard Batch Input Method ( LSMW).
Object 0060
Method 0000
Program Name RM06IBI0
Program Type B Batch Input
I am able to post data only for the condition type PB00. for other condition types FRC1 & FRA1 not able to post the data ( also session is not giving any error).
Therefore I am trying out witH BAPI option ( BAPI_PRICES_CONDITIONS),
when i try to test the BAPI i am getting an error "Record KNUMH = 0000668598,
VARNUMH = 000000000000000000000000000000: det. data missing ( Structue BAPICONDIT) .
i am passing below mentioned values to the structue BAPICONDIT
OPERATION 009
SD_DOC
ITM_NUMBER 000000
COND_NO 0000668598
COND_COUNT 02
APPLICATIO M
COND_TYPE FRC1
SCALETYPE F
SCALE_QTY 0.000
SCALE_VAL 1.000000000
CURRENCKEY USD
CURREN_ISO USD
CALCTYPCON C
COND_VALUE 2.000000000
CONDCURR USD
COND_ISO USD
COND_P_UNT 1
COND_UNIT KG
CONUNITISO KG
NUMCONVERT 1
DENOMINATO 1
BASE_UOM KG
BASEQTYISO KG
CONDITIDX 01
Please Suggest what else needs to be passed to get the BAPI working.
Regards,
Sriram

Hi Phemmy,
it is possible to create PO before info record .info record establishes the relationship between vendor and your particular material.
to answer your 2nd question:
it is possible to create inforecord automatically during PO creation. in the ME2N screen, in the material tab, put the material code. then go to item details.in the materail data tab, you will get infoupdate check it.and then inforecord will be created automatically.
Thanks
Nisha
Edited by: nishaprasad on Jan 14, 2010 11:29 AM

Extended Purchase Info Record using with LSMW

HI guru's,
How to extend purchase infor record using with LSMW programm.. what is the T.Code and important fields.
regards
JK

Hi,
You will need to create an LSMW programme for this, the source fields will be as below
LIFNR     Account Number of the Vendor
MATNR     Material Number
EKORG     Purchasing Organization
WERKS     Plant
MAHN1     Number of days for first reminder/urging letter (expediter)
MAHN2     Number of days for second reminder/urging letter (expediter)
MAHN3     Number of days for third reminder/urging letter (expediter)
APLFZ     Planned delivery time in days
UNTTO     Underdelivery tolerance limit
EKGRP     Purchasing group
NORBM     Standard purchase order quantity
MWSKZ     Tax on Sales/Purchases Code
NETPR     Net price in purchasing info record
WAERS     Currency Key
LTEX1_02     Long Text
LTEX2-02     Long Text
LTEX3-02     Long Text
LTEX4-02     Long Text
LTEX5-02     Long Text
LTEX6-02     Long Text
LTEX7-02     Long Text
Regards
Merwyn

IDoc status 51 - LSMW for Creating Purchasing Info Records

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

I shouldnot use basic type INFREC01 instead of NFRECMASS01.
'coz Within the FM there is a check for basic type like:
check idoc type
if f_idoc_control-idoctp c_idoctp_infrec01. " INFREC01
raise wrong_function_called.
endif.
Even one can go to WE57 and see the basic Type INFREC01 assigned to the FM IDOC_INPUT_INFREC, hence one shud use this basic type...

Bapi for creating purchase info records

Hi,
Is there any bapi or standard function to create PIR

BAPI_REQUISITION_CREATE
or
ME_CREATE_REQUISITION_EXT
see this list as well.
http://www.sapbapi.com/bapi-list/

Creating Purchasing info records using transaction ME11

Similar Messages

Maybe you are looking for