Error in CIF for Purchase Info Records

Hi,
I am trying to CIF Purchase Info record from R/3 to APO but its getting stuck during activation "generating delta Model".
Can anyone please help in this regards, I have already read the link related to BD22 but which message type do we need to delete. Also what can be the other reason.
I have CIFed Plant, material, vendor in the same sequence also I have extended material to vendor manually in APO.
I have one more issue the vendor code 1000000 in R/3 is getting create as 0001000000 in APO can this cause a problem
Thanks,
sanjog

Hi Sanjog ,
Iam not sure why you are looking at tcode BD22. It is not relevant to PIR transfer .
Also to CIF the PIR for a material from R/3 to APO, it is not necessary that the material should exist in the vendor location in APO. (You need to create the material at vendor location only if it is required specifically for your business scenario).
Now , to identify what is causing the problem , you have to check the inbound queue in APO and outbound queue in R/3. The tcodes are SMQ2 and SMQ1. You can also use the queue manager /n/sapapo/cq in APO . Check what the error message is and correct the master data in R/3 accordingly. Then delete all blocked queue entries (/sapapo/cq can be used ) and then run the PIR CIF activation again.
Thanks
Saradha

Similar Messages

Document type for Purchasing Info Records

I want to know where do we define the document type( IL, IN ) for Purchasing Info Records in Customizing(SPRO).
Are these standards or can we define new document types?

Hi
There are 4 categories of info records.
Standard
Subcontract
Consignment
Pipeline
There are two types of Info records maintenance:
1) Cross-plant (where you can maintain your info record at the purchasing organization level); or
2) Plant specific (where the specific plant must be maintained).
Besides, there are two document types of info records being hardcoded in SAP -
1) Purchasing Info Record for stock materials (Document Type IL); and
2) Purchasing Info Record for Material Group (Document Type IN).
regards
Srinivas

None approval process for Purchasing Info Record

Hi,
Are there some approval process in SAP for Purchasing Info Record?
Now, we use ME11 to creat Purchasing Info Record. And use ME12 to modify Purchasing Info Record. I feel it is very dangerous. Becase if someone make a mistake. Nobody know.
If the price is lower than actual price, vendor must ask us modify it. If the price is higher than actual price, I am not very sure what will happen.
So, we are seeking for an approval process in SAP system.
Dan Yang

>
DanYang!@# wrote:
> Hi,
>
> Are there some approval process in SAP for Purchasing Info Record?
> Now, we use ME11 to creat Purchasing Info Record.
And use ME12 to modify Purchasing Info Record. I feel it is very dangerous.
Becase if someone make a mistake. Nobody know.
>
> If the price is lower than actual price, vendor must ask us modify it.
If the price is higher than actual price, I am not very sure what will happen.
>
> So, we are seeking for an approval process in SAP system.
>
> Dan Yang
There is no approval process in standard,Since it serves as master.
Better provide authorization for ME11 & ME12 to restrict it.
Raise quotation to maintain vendor prices.

Number Ranges for Purchasing Info Record

Dear Guru's
Number range interval for Purchase info record can be created and assign to group and there are two group for Stock and Non Stock materials.
Now my query is how the system pick the number range ??? Since we don't have any assignment like PR,PO
My requirement is we have 3 company code - I need to have different number ranges for purchase Info record for each company . Guide me to achieve ...
Thanks in advance
Regards
Anand

SAP has provided only Two standard document Types for Pur. Info Records.
IL for Stock Material ( with matl No.)
IN For material Group (w/o MMR).
By default, if you enter Matl No. in the initial screen, system automatically picks the doc. type IL and the no. range assigned to it.
If you're not entered matl. no. in the initial screen, and proceed the Transaction further, system picks the doc. type IN and prompts you to enter Matl Group.
In the second case, the system picks up the no. range as per assignment.
Here in your case, you want create a new no. range and assign to your IL/ IN.
For this, you go to the transaction Define No. Ranges in Inforecord, from menu bar, choose Group-> maintain. Here you maintain your new no. range with a name. Now your new group is created with your required no. range.
Then select your new group ( Check box), select, IL, and click assign button and save.. Your IL is assigned to your new group and system picks the new No. Range when you are creating a Inforecord with Mat No. Similarly, you can change No. range for IN also.
or one more option you have.
In the first screen of No. Ranges Transaction, select change intervals tab button, you'll be goto intervals screen. There, from Menu bar, choose Interval-> change current No. Then you reset your current no. to Zero, save it. The again choose Change Interval, then in that screen, change the Interval with your new no. range.
Here in the second case, u need not maintain new groups. Just changing the Interval for the existing group.
You can adopt any one of these options.

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.

APO CIF issue - Purchase Info Record not getting CIFed from R/3 to APO

Dear All,
We are unable to CIF Purchase Info Record from SAP R/3 to APO. Are there any special setting that needs to be done for the same. We have created an Integration Model and using tcodes CFM1/CFM2 but without any success. Can anybody throw some light on this issue?
Thanks in advance
Ehsan Ahmed

Ehsaan
Can you check the SLG1 logs in R/3 and APO sides for further clues? Try to confine the time range to the exact time of activation of Purch INfo record model.
Maybe you have already done this check. Can you go to the Purchasing tab of Material Master and see if the Source List checkbox is unchecked ? Do you have any special procurement keys defined by any chance ?
Regards
Srinivas

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

BDC for Purchase info records in AFS

Hi Everyone,
I could not found any BAPI,IDOC,FM with supports for uploading purchase info records in AFS, is the only way is to do is recording or any thing else supports.
Regards,
Srinath.

Hi Srinath,
You have posted on a wrong forum. Please close your thread.
You may check this thread and post to your question there:
*The operation cannot be carried out with this node type*
Thanks,
Gordon

Customizing the Enjoy PO document overview for Purchase Info Records (PIR)

Greetings!
I am looking to use purchase info records to store material pricing information but we donu2019t want to lose the document overview functionality that SAP delivers with the enjoy PO screens (ME21n, ME22n, ME23n).
Has anyone had success implementing user exit MEQUERY1 to customize the document overview so that a purchase info record query can be added to the document overview & the attributes of the purchase info record can be copied over to the PO?
Iu2019d be curious to know what solutions other SAP shops came up with.
Thanks.
Richard Wortmann

Nick,
Thanks for the reply. We will have the source list generated for the purchase info records (PIRs) however the gap I'm looking to solve for is mainly for non-MRP material buys.
Our current business situation allows material handlers to run a query in the document overview to ID specific materials on a purchasing contract (aka outline agreement) and drag those materials to the shopping cart on the PO. This provides a very easy process for the buyer to ID materials & supplier relationships.
Since we are moving away from purchasing contracts we want to continue with the same drag and drop process but only allow PIR's to be selected in the query.
Looks like in OSS note 377180 SAP provides a user exit to implement this functionality (via MEQUERY1)- I'm just wondering if anyone has had success adding a PIR query to the document overview and creating POu2019s with reference to that query.
Thanks.
Rich Wortmann

Urgent !!! User exits or badi for purchase info records

Hi all,
In purchase info records that is through tcode ME11, ME12 I need to validate order unit field. When you go to tcode ME12 in the second screen you will find order unit field. Now the thing is I need to validate this field. For example when the user selects any unit type I need to pass value to a custom field based on the value of order unit field. Please let me know who to carry out this process.
Thanks in advance.
Andy
Message was edited by: Andy V

Hi Andy,
I'm not sure is those transactions has Badis, but if you want to make sure of it (I can't do it right now), go to SE80 transaction and select the class/interface CL_EXITHANDLER, then you have to select the Get_Instance method and put a break-point in the following call:
call method cl_exithandler=>get_class_name_by_interface
exporting
instance = instance
importing
class_name = class_name
changing
exit_name = exit_name
exceptions
no_reference = 1
no_interface_reference = 2
no_exit_interface = 3
data_incons_in_exit_managem = 4
class_not_implement_interface = 5
others = 6.
the value of exit_name will give you the name of the BADI that is been call from the transaction.
Note: This method will show you every Badi that is being activated since you put the break-point.
Regards,
Eric

Pricing schema for purchase info records

hi guys!
does anyone knows either SAP standard got function to define pricing schema for PIR? if yes, can you please tell me how to set it up step by step?
Thanks a lot,
crystal.

Hi,
there is no separate pricing schema for reading info records.
When creating PO, the system first searches for a purchasing
info record with the combination of vendor/material at purchasing
organization/plant level. If there is no such info record, the system
then search at purchasing organization level. If there is no such
info record here either, you must enter it manually.
If the purchasing info record exist, then valid conditions have
priority during price determination. If an info record does not
contain any conditions or invalid conditions, the system read from
last purchasing document in the info record and then suggest the price
from here. The price determined in this way are default values that
can be changed by the buyer if necessary.
You can save useful quotation data for a material in purchasing
info record. The info record can be created automatically by
setting the info update indicator during quotation maintenance
in the item detail.
Please first check is there any valid info record exist for this
material/vendor. You can always create/change/view it manually
via Ta ME11/ME12/Me13.
Please read also the notes 392988, 456691.
Regards,
Edit

Minimum price for purchase info record

Hi
For some supplier, we need to set up a minimum price in purchase info record condition as show in example.
Price / pce : 50.00 CHF / 100 pce
Minimum price : 200.00 CHF
So price for PO should be for X quantity : Min(200, X * 50 / 100)
Is it possible to do that? Our internal competence center says us that it's not possible, but i would like your opinion.
Thanks for your help

Hi,
If you want to scale up your price as per quantity in PO, it can be done. for example for 60 quantity price is $100 and for 70 quantity it is $95.
Go to Transaction M/06 and select the base condition PB00. Make sure the 'Group Condition' indicator and 'Rounding Difference Comparison' indicator should be activated and the 'Group Condition Routine' field should be entered with '1' (Overall Document).
2) Maintain your purchasing info record for Material A where the Condition Group should be set (ABC, for instance). Select the base condition PB00 and then set up the scaled pricing value (Y, for instance).
3) Maintain the PO for Material A . Upon completion of maintenance, click on 'Check' icon to activate the Pricing Determination. You will see that the pricing Y is applicable to Materials A.
Regards,
Ahmad Farhan Khalid

BAPI for Purchase Info record creation - ME11 transaction

Hi,
Is there any bapi or function modules which will create the Purchase info record in Me11 transaction and also bapi for change Purchase info record in Me12 transaction?
Points will be awarded.
Regards,
vinoth.

Hi,
ME_MAINTAIN_INFORECORD
ME_UPDATE_INFORECORD
ME_GET_INFORECORD_CONDITIONS
ME_PRICING_INFORECORD.
ME_DIRECT_INPUT_INFORECORD
ME_POST_INFORECORD.

Bapi for Purchasing Info Record

Hi,
Is there any Bapi for creating Purchasing Info Record, Transaction code ME11.
How do we generally go about it.
-Thanks,
Sneha.

I'm also looking for an function module or a BAPI, so I hape that anybody will give us a hint
Thanks

BAPI for Purchase info record creation

Hi
Please let me know how to create purchase info record through BAPI, with tax codes along with material price.
please guide me.
Simha

Hi,
ME_MAINTAIN_INFORECORD
ME_UPDATE_INFORECORD
ME_GET_INFORECORD_CONDITIONS
ME_PRICING_INFORECORD.
ME_DIRECT_INPUT_INFORECORD
ME_POST_INFORECORD.

Error in CIF for Purchase Info Records

Similar Messages

Maybe you are looking for