Limitations for CIFing a material

Hi,
Do we have any limitation to CIF a material to APO? I mean what are the prereqs to successful transfer of material from R/3 to APO, except Cifing the plant before materials.
Any thing or MRP group, type, etc....??
I am trying to CIF a material with strategy group 52 (Plnng w/o final assem. w/o make-to.stock) but the material is not CIFed and I don't see any thing in SMQ1 in R/3 or SMQ2 in APO... just wondering what might have happened.
MY CFC9 setting for Material Master Change Transfer is 2 (BTE Transfer, Immediately)
Thanks.
Edited by: Raj G on May 9, 2008 11:08 AM

Hi Raj,
For an Initial Transfer of a Material, only the Location will need to be trasferred first.
Also, the CFC9 setting you had mentioned will be relevant for change transfers and not for an initial transfer.
What I think could be the problem is a Filter Condition for the Material which could have been set in CFM1, during Generation of Integration Model. It could be that that the Material was not taken into consideration at all during Generation/Activation of the Integration Model, and hence was not transferred.
Hope this helps.
Thanks and Regards,
Sharath Krishnan

Similar Messages

Limits for packaging Material

How Do I set Limit for packaging Material.
For eg: Packaging Material PALLET should only contain
50 units or less .

Hi
After production order creation or release run the COMAC transaction with all VERP materials or with MRP controller selection as well
In mass processing - material availability check select scope of process. you can create variant here and schedule back ground job
after execution see the missing parts list with reqmt qty, committed qty and shortage in CO24 TCode
Regards
Dev

Tolerance limits for contract

Hi all,
   Is there any possibility to maintain tolerance limits for Quantity in Quantity Contract (doc type MK),,,
ex: Quantity Contract (MK) -- target quantity = 100
      it should allow me to create release orders (Purchase orders) for 105 quantity(tolerance of +5%)
regards
urendra

Hi,
By using Purchasing Value Key in Material Master you can control over and under deliveries.But its applicable to that material.
If Purchasing Info Record exists for that material then tolerance limit which is given in inforecord takes priority.
Regards,
Ramesh
Message was edited by:
        Ramesh

Tolerance limits for Price Variation

Dear All,
I have set the Following in Customizing.
In the following node : IMG-------> Materials Management ----------> Purchasing -----------> Purchase Order ---------> Set tolerance limits for price Variance.
In this, For Company code & Tolerance Key "PE" combination, it has been set " Check Limit 20%" in the Percentage field ( Upper limit ).
Now, I have a material having a Moving Average price of 100 INR in the material master Accounting view. When I create a PO for 130 INR, there is no warning/error message that is popping up? Isn't the system supposed to throw a message here, since 130 inr exceeds 120 INR, or am I missing something out here ?
Note : 120 INR = 100 + (20%)(100) = 120 INR.
Regards
Sathya

Hi Sathyanarayana Rao V N
You can benefit from M8 messages for incoming invoices with tolerances to solve your problem. You have to configure your system messages with error.
Regards.
M.Ozgur Unal

Tolerance limits for PO,MIGO..etc..?

Dear all
Can anybody explain me about the tolerance limits in SAP-MM,
1.what is tolerance limits..?
2.Why tolerance limits need in SAP-MM..?
3.How to configure in SPRO
Which are all the area has to maintain Tolerance limits according to MM point of view
Advance thanks
goods answers will be highly rewardable.
Thanks
sap-mm

Hi
tolerance limits for price variancesin Purchase order
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
For Invoices specify the tolerance limits for each tolerance key for each company code.
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Thanks & Regards
Kishore

Tolerance Limits for Date and quantity..??

Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.

Hai
for quantity tolerence limit u can do it while creating P O in item details-->delivery tab.
for date go to SPRO-->mm>purchasing->material master> define purchase value key>in that st.del.time var here it wil compare the dates and shows how much deviation is occuring for GR date
configure messages in SPRO-->mm>environment data--> define attributes of system messages
hope it may help u
regards
chandrasekhar

Maintain tolerance limits for tolerance key PE (CoCode S001)

Dear all
im getting error when i creating PO
Maintain tolerance limits for tolerance key PE (CoCode S001)
Please help me
Regards
venu gopal

Hi
You need to maintain the Tolerance key
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
Maintain the tolearnce key in
SPRO-> IMG-> Materials Management-> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
If you want the sytem to propmt for a warning or Error message you can configure the same in
SPRO-> IMG-> Materials Management-> Purchasing-> Environment Data-> Define Attributes of System Messages

PR, PO, GR for a consumable material without material master record

Hi,
I have created a complete cylcle till Invoice Verification for a material without a material master record.
But i have one query i.e. in the cylce i created i had to create a GR before entering MIRO. Is there any way by which i need not create a GR for a consumable material i.e. to be posted directly to a GL without any inventory management.
In my case, the GR checkbox in the PO was automatically ticked.
Can anyone help on this please.
Regards,
Laxmi

Customizing Error Message in ME23N
When displaying of modifying Purchase Orders with a document type of Framework Order, a user selects the LIMITS tab, they get the error message Customizing incorrectly maintained, message number SE729.
The problem is caused by version upgrades of the SAP software.
Number of entries in table T162V is different to the number of columns in table control for screen SAPLMLSP (400). You can use screen painter SE51 to display the screen. View the Element list for TC_VIEW.
The list of fields can also be viewed within the program. Transaction code ML81N (service entry sheet), program SAPLMLSR. Click on the Configuration button (top right hand corner) select Administrator. This shows the number of fields as 67.
Using SE16N to view table T162V shows 69 fields. This table contains six layouts (variants), they must all be the same. Before the change the total count was 414 (69 x 6).
The ME23N transaction only checks that the number of entries is correct. You will notice that the fields are not in the same sequence, but that should not matter if you donot use the service transaction ML81N and it is not a selectable tab on ME23N.
Transaction SM31 was used to delete the extra fields. As this is a SAP table, you may need extra authorisations to make the change.
Note: the number of fields shown above will be different in each site. This is because of different SAP versions and in what software is loaded.

Purchase Requisition for non valuated material

Hi,
We have defined a material as non valuated in ECC, we are doing planning vfor the material in APO and generating Purchase Requisition on vendor for the material. Now the issue is that we are not able to CIF the Purchase requisition to ECC and system is giving account assignment error.
For the same plant vendor locatio n combination Purchase requisition is getting CIFed for valuated material.
Canm anyone please help regarvding how to CIF purchase requistion for non valuated material from APO to ECC.
Thanks & Regards,
Sanjog Mi shrikotkar

Hi Sanjog
Agreed : the material is non valuated so we have not extended accounting view for the material, also we cannot allow financial posting for non valuated material.
But an accounting view is required for a material, no matter whether it is a valuated or a non valuated material
I am sorry about not being able to transmit any positive reply to you, i am not aware of other way of getting it
Best Regards
Vinod

Set Tolerance Limits for Price Variance for PR missing from SPRO

I'm looking into setting up tolerance limits for price variance at the PR level. But when i navigate here:
SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance
I'm not seeing that available in SPRO. It's available for PO's but not PR's. We want to be able to set tolerances on the PR to be applied to the PO for non stock items (material master). Please advise

Hi,
There is no standard configuration option to set the tolerance limit at PR level. You may set the tolerance limit for PO and control the price change. If you want the same functionality at PR level, then you have to go for development. Please check whether the BAdI: ME_PROCESS_REQ_CUST can fulfill your requirement. You may set the tolerance limit in OLME - PO - Set Tolerance Limits for Price Variance itself and write the logic in the BAdI to check the price variance in PR based on the same configuration (table T169G and similar).
You may check the similar thread: PR VS PO Price Tolerance
Regards,
AKPT

Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI?

Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI
I am trying to create a Sales Order using a Zprogram. I have used BAPI_SLSTRANSACT_CREATEMULTI. If I give the input as Normal material I am able to generate a sale order. If I give the input as VC material I am able to generate a sales order. But if I give both VC and Normal material as input, I get a run time error as follows.
Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI that we cannot create a sales order with both VC and Non-VC items or am I missing some data which I need to pass when I give both VC and Non VC items? I get this error only for my Zprogram. But if I try to create an order on screen manually I donu2019t get any error. This happens only if I create an order with my Zprogram.
Some one please help me u2026I am just stuggling to get this doneu2026
I dint find any posts that gives me information about this error.
CUX1 034 u201CNo root instance found in header datau201D
In the source code you have the termination point in line 63                                   of the (Include)program "LCRM_CONFIG_OWF02".
Line
SourceCde
33
LT_CUXI_CUPRT
34
LT_CUXI_CUVAL
35
LT_CUXI_CUVK
36
LS_CUXI_CUCFG.
37
38
PERFORM CREATE_PRICING_CSTIC USING IS_CONFIG-CUCFG-CFGINFO.
39
40
set config to cbase
41
CALL FUNCTION 'COM_CUXI_SET_SINGLE_CFG'
42
EXPORTING
43
I_CFG_HEADER          = LS_CUXI_CUCFG
44
I_ROOT_INSTANCE       = CV_INT_OBJ_NO
45
I_LOGSYS              = LV_LOGSYS
46
IMPORTING
47
E_ROOT_INSTANCE       = CV_INT_OBJ_NO
48
TABLES
49
I_TAB_INSTANCES       = LT_CUXI_CUINS
50
I_TAB_PART_OF         = LT_CUXI_CUPRT
51
I_TAB_VALUES          = LT_CUXI_CUVAL
52
I_TAB_VAR_KEYS        = LT_CUXI_CUVK
53
I_TAB_RESTRICTIONS    = LT_CUXI_CURES
54
EXCEPTIONS
55
INVALID_INSTANCE      = 1
56
INTERNAL_ERROR        = 2
57
OTHERS                = 3.
58
59
IF SY-SUBRC <> 0.
60
if sy-msgno is initial.
61
MESSAGE X010 WITH 'COM_CUXI_SET_SINGLE_CFG'.
62
else.
>>>>>
MESSAGE ID SY-MSGID TYPE 'X' NUMBER SY-MSGNO
64
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
65
endif.
66
ENDIF.
67
68
ENDFORM.                               " CONFIG_TO_CBASE
Edited by: jessica sam on Jan 22, 2009 9:58 PM

Re: Can we create saleorder for VC,Non-VC items with BAPI_SLSTRANSACT_CREATEMUL

Limits for pricing in the VK11 - Max Value

Hi,
I am working on ECC 6.0.
I have been trying to use the Max number of orders and Max cond value for a Z condition type . The Max number of orders seems to be working, if I set to 2 the 3rd order does not have the condition type at all.But when I set the max condition value
it is not working even after reaching the max condition value. If anyone has faced such an issue before kindly help.
I had set the limits for pricing in the VK11 - Max Value condition,But of no use.
My calculation type is percentage and the scale base is value in the condition type.
Regards
Manoj

Hi Manoj,
If u r maintaing Max condition value
For exp: Material Price A= $100
max condition value is = $10000
when u creating 1st order with this material for 50 qty = $5000 is completed
for 2nd order if u r taking 100 also system will put the net value is $5000 only it will not consider remaining 50..
if u r placing 3rd order with any qty then net value will come zero..
that effect u can find from this..
if i am wrong plz corect mee..
Regards
Durga Prasad

Report for Comparison of Material Qty

Hi All,
I need to Develop an Interactive report for Comparison of Material Qty. ordered through Purchase requisition, ordered material through PO and corresponding Material Receipt report.
Can Someone Give a brief description about this & fields tcode & tables regarding this report.A sample code would be much appreciated.
Thanks & regards,
Ravi S

To get the material number combined with the PO text you will need the help of an ABAP programmer. The programmer can create a report for you using the function module READ_TEXT in the function group STXD. The tables to use are:
STXH - STXD SAPscript text file header
STXL - STXD SAPscript text file lines
The selection screen should have at least the following:
OBJECT - STXH-TDOBJECT
NAME - STXH-TDNAME
LANGUAGE - STXH-TDSPRAS
TEXTID - STXH-TDID
You find the information for these fields by going to the PO text entry screen and displaying the header information under Goto -> Header. For materials, the object is MATERIAL, the name is "material number", the language is "EN", and the text ID is BEST. You can use this program to get long text in lots of places like information records, purchase order texts, etc.
Hope this helps.

Memory limitation for session object!

what is the memory limitation for using session objects?
venu

as already mentioned there is no actual memory limitation within the specification, it only depends on the jvm's settings
how different app-server handle memory management of session objects is another part of the puzzle, but in general you should not have problems in writting any object to the session.
we had the requirement once to keep big objects in session, we decided to do a ResourceFactory that returns us the objects, and only store unique-Ids into the session.
We could lateron build on this and perform special serialization tasks of big objects in the distributed environment.
Dietmar

How to get the salesprice and condition for a customer / material / date

Hi all,
how can I get the correct price and condition for a customer / material / date ?
I know this is possible using the BAPI_SALESORDER_SIMULATE, but this bapi is using to much ressources on the system.
I'm trying to get the correct price and condition WITHOUT using that BAPI.
Does anyone know how it is possible ? As said before : I have the customer, material and a date.
thanks in advance for your help

Hi
You need it because it's possible to have a complex pricing procedure, and you can't do it with a simple select on a table. Think that you can have pricing requirements, formulas (ie: VOFM) and so on in your pricing procedure (tcode V/08).
I hope this helps you
Regards
Eduardo

Limitations for CIFing a material

Similar Messages

Maybe you are looking for