Vendor Master: Minimum Order Value
I am new to supporting MM and there is a question about Minimum Order value on the Vendor Master (LFM1-MIMBW)
It is not currently used.
Can we simply start populating it?
Can it be populated for only specific vendors?
What specifically will it do for us?
Are there draw-backs?
Is it "safe" to test?
Thank you all for information
Althea
No problem at all in using Minimum Order value in Vendor master
It will only applicable for that vendor and only for MRP generated PR's and convertions of those PR's to PO's.
It is populated for the only vendors in which u maintain this.
Drawbacks - If the requirement is of 10 pcs but minimum order value is 100 then system creates the purchase proposals for 100 which may increase ur Inventory./
Yes it is safe as it doesnot involves any configuration and it is only a master data activity.
Regards
Vineet Baweja
Similar Messages
-
Minimum order value in vendor master - error message in SRM
Hello!
I am using minimum order value in ERP for some vendors and I am wondering if is it possible to get the same error message in SRM.
While creating a shopping cart in SRM if the minimum order value is not reached, the following document created is a purchasing requisition.
I would like to get the error message that the minimum order value is not reached instead of the automatic creation of a purchase requisition.
Is it possible?
Thanks in advance!
Best regards,
KarinHi Karin, if you need to show an error message during Shopping Cart creation you willl need to implement badi BBP_DOC_CHECK_BADI, and maybe create an RFC Function Module to check in ECC ir the minimum order value was reached or not and show the error message.
In order to control the following document you will need to implement badi BBP_TARGET_OBJTYPE.
Find bellow a sample BBP_TARGET_OBJTYPE - Code Approach.
Hope This Help.
Celeste -
Minimum order value for Purchase orders
Hello,
This is my requirement: -
A condition type needs to be created for Minimum Oder Value for PO. If the PO value is say, 450 and the condition record in 500, the PO value must be adjusted to 500. If PO value is 550, then it remains 550.
1. Condition records must be maintained.
2. Must be calculated on whole PO (all items) and then redistributed among items in a suitable ratio.
This is what I have already tried:-
1. Vendor master - No use maintain minimum order value as PO price must be adjusted through condition types.
2. Tried replicating PMIN condition type and it works but only at item level - this calculation must take place at header level. Also it works only for calculation type "Quantity".
Please suggest how this can be implemented, hopefully through configuration only.Hi,
Please use user exit MM06E005 and code accordingly. Take help of ABAPer.
thanks and regards
Murugesan -
Merchandise Distribution Collective PO with SLS - Minimum Order Value
Hi,
My organisation is using Merchandise Distribution with SLS to generate collective PO's at our consolidation platforms before generating either STO's or PO to the supply source.
We're utilising Cross Dock and Flow Through to support our processes but in the case of Cross Dock, we're essentially asking the supply source to pick/pack the stock for the final recipient, therefore it can be quite an expensive process for the supply source (but clearly not for us).
Before we implemented this the supply source used to simply receive orders directly from the store and within this process we applied Minimum Order Values, as per my previous statement it can be expensive and picking a couple of small items for one store and having to put them on a pallet is not economical for them in either warehousing or transportation.
I'm looking for some broad suggestions on how this could be achieved whilst utilising collective orders.
Our store STO's generated by MRP (and soon enough F&R) are large STO's that are not truly supply source specific, they are consolidation platform specific and the collective orders generated off the back of them are supply source specific.
The key issue i see is that we're asking for a select group of lines within the store STO to meet an MOV of the vendor OR that we somehow ensure that the store STO's are supply source specific and then enforce some MOV logic.
Obviously this isn't standard but it's causing our organisation big supply issues, so any thoughts or advice would be fantastic.
Many thanksHi ,
You can not do directly in ME59N. Check for user exit for this t code.
Thanks,
Venkat -
Minimum Order Value for an internet sales order in the webshop
Hi Guys,
I have a requrement of maintaining Minimum Order Value (MOV) for an order created in B2B webshop.
We have a condition type AMIZ which supports the same function in ECC. Will it support CRM too?
Current implementation is CRM 5.0 and the backend is R/3 4.7.
Thanks in advance,
SrinivasHi Srinivas,
I believe condition type AMIZ is available in CRM by standard. So its should support. Offcourse you ll have to assign the required requirement routines / condition base values.
Regards,
Gaurav Gera -
Freight calculation on minimum order value
Forum,
I am wondering if it is possible for Freight to be calculated on an AR Order based on an order's minimum order value. i.e. If an order with a value of <£50 then £5 Freight is applied.
I cannot see a standard way of doing this, can this be confirmed?
Regards,
JuanHi Juan,
There is no standard way for it. You can try FMS.
Thanks,
Gordon -
Use of minimum order value condtion AMIZ and AMIW
I am using the above standard SAP conditions to calculate a minimum order value. It is working fine for an order with a single order item but for multi-item orders it is only doing the calcualtion for the last item. As per standard SAP i have AMIW defined as group condtion but this seems to being ignored.
Do I need to also fill in the Group Condtion Routine (GRLNR) on AMIZ or AMIW in order for this to work?
Regards
Dave JonesSettings in Pricing Procedure
You must enter these condition types in the pricing procedure you use. The following settings are required:
Condition type AMIW
Field Value
Statistical X
Subtotal D
Account key Blank
Condition type AMIZ
Field Value
Alt.calc.type 13
Account key ERS
Using Referenced Conditions
The minimum order value function uses referenced condition records. Condition type AMIZ references condition type AMIW. Referencing conditions means that different condition types can share the same condition records.
Creating Condition Records
If you use minimum order value requirements, you must create condition records for condition type AMIW. In these condition records, you specify customers and the corresponding minimum order values. During pricing, the system automatically uses these condition records as a reference for determining the relevant minimum order value surcharges (Condition type AMIZ).
If you want to specify minimum order values that are not customer-dependent but instead are based, for example, on a sales organization, you must create a new condition table with the appropriate key.
Dependent functions
Condition referencing is controlled by two fields in condition type definition. For minimum order value processing, the settings for condition type AMIZ are as follows:
Field Value
Ref.condition type AMIW
Ref.application V -
Cancelling order discounts when below Customer's Minimum Order value
I've been reading what I can find about discount conditions etc and am slightly confused as all the examples seem to relate to item line situations. We need to have a setup where all possible discounts are cancelled if the order total value is less than a given minimum order value (or threshold) related to that particular customer - and not based upon any line item value.
We do not use Minimum Order Value as per the SAP examples given i.e. orders not accepted below the MOV and therefore surcharges added. As mentioned we use a threshold value for most customers under which discounts do not apply.
Because of this we cannot automatically email or fax acknowledgements, and we have a massive time consuming checking operation for orders added to ensure mistakes are not made i.e. discounts applied incorrectly before the acknowledgements are sent out.
Can anyone advise as to where I can find the path to getting a solution to this problem.
Thanks
Jim Jackson
Edited by: Jim Jackson on Feb 20, 2009 9:11 AMI understant AMIW is Header condtion type - statistical- and has the MOV value for the specified customer.
Maintain AMIW as Header / Line condition type.( T Code V/06)
Create the condition reocord for AMIW with EXCLUSIVE Indicator X.(VK11)
Then create a requirement for all the discount condition types, if the total order value = or > AMIW value then do not check the exclusion indicator( KOMP - KZNEP), ELSE check the exclusion indicator.
( T Code VOFM)
During order save - automatically repirce the order in Userexit_save_document_prepare or userexit_save_document.
If there is a partial delivery, during Invoicing if the copy control(delivery to Invoice) has carry out new pricing B, the above setting might fail. Maintain the copy control setting to copy pricing elements unchanged and redetermine taxes OR try to determine the condition values in the invoice from the order.
Hope this helps.
Thanks
Sai -
Minimum order value for delivery
Hi all,
I have a problem concerning order value. I want to block orders for delivery that, based on the shipping point for the individual items, do not reach a minimum order value per shipping point. When the customer orders the next time and the combined value on a specific shipping point for the old and the new order(s) reaches the limit, a delivery document should be created. We also want to create a message to the customer saying that the first order wasn't delivered due to low value.
Is this possible without extensive programming? A little coding in a copying rule or such is ok, but as we can handle this manually in the WH-system we don't want to put to much effort in it.
best regards,
GlennYes you can do that, You can use the mimum order value condition type in the pricing procedure . This condtion type check for the mimimum order value and if this is not met based on the routine in pricing procedure it will block. You can make adjustments in code for the routine for the condition type.Condition type is AMIW
Reward points!!!!!!!!!!1
Thanks,
Kamal -
Hi All,
We are trying to use the standard condition type AMIW and AMIZ to achieve the minimum sales order processing, but for some reason this does not seem to work.
Per OSS Note 999587,18173 we have the necessary condition type maintained as well as they have been included in the pricing procedure as mentioned in the note.
The issue is although the minimum value is not reached, the corresponding surcharge condition has a value of 0. subtotal has been assigned value 'D' for AMIW however WORKD has a value of 0.
Settings in pricing procedure
Condition type AMIW
Field Value
Statistical X
Subtotal D
Account key Blank
Condition type AMIZ
Field Value
Alt.calc.type 13
Account key ERS
We have also setup the condition record, with a fixed value of 200USD for AMIW. I was hoping by using this function the system would determine a minimum order surcharge value if the net value of the order was below 200USD.
Has anyone been able to use the minimum sales order value function? We are currently on ECC6.0 and our patch level for SAP_AP is at 0020 release 700.
Any help or insight is much appreciated.
Thanks
LDHi,
http://help.sap.com/saphelp_46c/helpdata/en/93/7434de546011d1a7020000e829fd11/frameset.htm
Also assign Requirement as 2 and try
Kapil -
Minimum order value maintainance in B2B order
Hello Gurus,
We are on CRM 5.0. In b2b web shop, there is a requirement that order should not be saved if the value of the order is below a minimum value for all customers. Addition of surcharges as in AMIW / AMIZ is not what the business wants. We are proposing to either hardcode the values in the jsp page or store the minimum values in a z table and change the code in the order .jsp file such that a check is made in the z table on save. Is there a standard solution for this?
Useful solutions will be rewarded with points.
Regards,
SrinivasHi,
Try configuring from CRM side(similar to minimum order qty and pice) instead of specific custom enhancments.
regards,
laxman
Edited by: laxman on Mar 13, 2008 9:33 PM -
Vendor Master Extraction from Legacy
Hi guys,
We have 2 different legacy systems here (4.5b and 4.6c) and I am trying to extract the vendor master from both of them and integrate them into the new mysap2004.
What is the best way to extract the vendor master along with the address , punchasing doc, bank details, partner functions,etc ? Any sample program for vendor master extraction is most welcome. Here is my extract layout.
ADDRESS
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
SZA1_D0100 Title (TITLE_MEDI) CHAR/30 Not used
ADDR1_DATA Name (NAME1) CHAR/40 Bring values over as is.
ADDR1_DATA Name (NAME 2) CHAR/40 Bring values over as is.
ADDR1_DATA Name (NAME 3) CHAR/40 Bring values over as is.
ADDR1_DATA Name (NAME 4) CHAR/40 Bring values over as is.
ADDR1_DATA Search Term 1 (SORT1) CHAR/20 Convert to HPC methodology.
O-First 8 char. of vendor name
R- First 8 char. of vendor name
B- First 8 char. of vendor name
ADDR1_DATA Search Term 2 (SORT2) CHAR/20 Bring values over as is.
ADDR1_DATA Street/House Number
(Street) CHAR/60 Bring values over as is.
ADDR1_DATA House Number
(HOUSE_NUM1) CHAR/10 Bring values over as is.
ADDR1_DATA Building (number or code)
(BUILDING) CHAR/20 Bring values over as is.
ADDR1_DATA Room or apartment number
(ROOMNUMBER) CHAR/10 Bring values over as is.
ADDR1_DATA Floor in building
(FLOOR) CHAR/10 Bring values over as is.
ADDR1_DATA c/o name
(NAME_CO) CHAR/40 Bring values over as is.
ADDR1_DATA Street 2
(STR_SUPPL1) CHAR/40 Bring values over as is.
ADDR1_DATA Street 3
(STR_SUPPL2) CHAR/40 Bring values over as is.
ADDR1_DATA Street 4
(STR_SUPPL3) CHAR/40 Bring values over as is.
ADDR1_DATA Street 5
(LOCATION) CHAR/40 Bring values over as is.
ADDR1_DATA City
(CITY1) CHAR/40 Bring values over as is.
ADDR1_DATA District
(CITY2) CHAR/40 Bring values over as is.
ADDR1_DATA City (different from postal city)
HOME_CITY CHAR/40 Bring values over as is.
ADDR1_DATA City postal code
(POST_CODE1) CHAR/10 Zip Code. Bring values over as is.
ADDR1_DATA Country
(COUNTRY) CHAR/3 Bring values over as is.
ADDR1_DATA Region (State, Province, County)
(REGION) CHAR/3 E.g., NJ New Jersey, CO Colorado, etc. Bring values over as is.
ADDR1_DATA Time Zone
(TIME_ZONE) CHAR/6 Bring values over as is.
ADDR1_DATA Transportation Zone
(TRANSPZONE) CHAR/10 Bring values over as is.
ADDR1_DATA Regional Structure Group
(REGIOGROUP) CHAR/8 Bring values over as is.
ADDR1_DATA P. O. Box
(PO_BOX) CHAR/10 Bring values over as is.
ADDR1_DATA P.O. Box Postal Code
(POST_CODE2) CHAR/10 Bring values over as is.
ADDR1_DATA Language Key
(LANGU) LANG/1 Bring values over as is.
SZA1_D0100 Telephone
(TEL_NUMBER) CHAR/30 Bring values over as is.
SZA1_D0100 Telephone Number Extension
(TEL_EXTENS) CHAR/10 Bring values over as is.
SZA1_D0100 Fax
(FAX_NUMBER) CHAR/30 Bring values over as is.
SZA1_D0100 Fax Extension Number
(FAX_EXTENS) CHAR/10 Bring values over as is.
SZA1_D0100 E-mail
(SMTP_ADDR) CHAR/240 Bring values over as is.
ADDR1_DATA Standard Communication Type
(DEFLT_COMM) CHAR/3 Bring values over as is.
ADDR1_DATA Data Line
(EXTENSION1) CHAR/40 Not used. Do not bring over field values.
Note: This field will be available to populate with other data during the conversion.
ADDR1_DATA Telebox
(EXTENSION2 CHAR/40 Not used. Do not bring over field values.
Note: This field will be available to populate with other data during the conversion.
ADDR1_DATA Comments
(REMARK) CHAR/50 Bring values over as is.
CONTROL
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFA1 Customer
(KUNNR) CHAR/10 Bring values over as is.
LFA1 Authorization
(BEGRU) CHAR/4 It is to be determined if this field will be used in the future. If yes, bring values over as is from HPC and populate with vendor account group code for Foods.
LFA1 Trading Partner
(VBUND) CHAR/6 Bring values over as is.
LFA1 Group Key
(KONZS) CHAR/10 Not used
LFA1 Tax Code 1
(STCD1) CHAR/16 Bring values over as is.
LFA1 Tax Code 2
(STCD2) CHAR/11 Bring values over as is.
LFA1 Fiscal Address
(FISKN) CHAR/10 Bring values over as is.
LFA1 Jurisdiction Code
(TXJCD) CHAR/15 Bring values over as is.
LFA1 VAT Registration No.
(STCEG) CHAR/20 Bring values over as is.
LFA1 Tax Office
(FISKU) CHAR/10 Bring values over as is.
LFA1 Tax Number
(STENR) CHAR/18 Bring values over as is.
LFA1 Industry
(BRSCH) CHAR/4 Bring values over as is.
LFA1 Train Station
(BAHNS) CHAR/25 Not used.
LFA1 Transportation Zone
(LZONE) CHAR/10 Bring values over as is.
LFA1 Actual QM Sys.
(QSSYS) CHAR/4 Bring values over as is.
LFA1 QM System To
(QSSYSDAT) DATS/8 Bring values over as is.
LFA1 DAK
(J_1FDAK) CHAR/8 Bring values over as is.
PAYMENT TRANSACTIONS
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFBK Bank Country Key
(BANKS) CHAR/3 Bring values over as is.
LFBK Bank Key
(BANKL) CHAR/15 Bring values over as is.
LFBK Bank Account
(BANKN) CHAR/18 Bring values over as is.
BNKA Bank Name
(BANKA) CHAR/60 Foods - Bring values over as is.
HPC Populate with Bank Account Number
LFA1 Alternative Payee
(LNRZA) CHAR/10 Bring values over as is.
LFA1 Individual Spec.
(XZEMP) CHAR/1 Bring values over as is.
LFA1 Spec. Per. Reference
(XLFZA) CHAR/1 Bring values over as is.
ACCOUNTING INFORMATION ACCOUNTING
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFB1 Recon. Account
(AKONT) CHAR/10 Bring values over as is.
LFB1 Sort Key
(ZUAWA) CHAR/3 Bring values over as is.
LFB1 Head Office
(LNRZE) CHAR/10 Bring values over as is.
LFB1 Authorization
(BEGRU) CHAR/4 Bring values over as is.
LFB1 Cash Mgmnt Group
(FDGRV) CHAR/10 Bring values over as is.
LFB1 Release Group
(FRGRP) CHAR/4 Bring values over as is.
LFB1 Minority Indicator
(MINDK) CHAR/3 Bring values over as is.
LFB1 Certification Date
(CERDT)
DATS/8 Bring values over as is.
LFB1 Interest Indicator
(VZSKZ) CHAR/2 Bring values over as is.
LFB1 Last Key Date
(ZINDT) DATS/8 Bring values over as is.
LFB1 Interest Cycle
(ZINRT) NUMC/2 Bring values over as is.
LFB1 Last Interest Run
(DATLZ) DATS/8 Bring values over as is.
LFB1 Withholding Tax Code
(QSSKZ) CHAR /2 Bring values over as is.
LFB1 Withholding Tax Country
(QLAND) CHAR /3 Bring values over as is.
LFB1 Recipient Type
(QSREC) CHAR /2 Bring values over as is.
LFB1 Exemption Number
(QSZNR) CHAR /10 Bring values over as is.
LFB1 Valid Until
(QSZDT) DATS/8 Bring values over as is.
LFB1 Exemption Authority
(QSBGR) CHAR /1 Bring values over as is.
LFB1 Previous Account No.
(ALTKN) CHAR /10 Do not bring over existing values. Will populate during vendor conversion when legacy vendor number is replaced by a new vendor number.
LFB1 Personnel Number
(PERNR) NUMC/8 Bring values over as is.
PAYMENT TRANSACTIONS ACCOUNTING
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFB1 Payment Terms
(ZTERM) CHAR/4 Refer to data mapping spreadsheet later in this spec.
LFB1 Tolerance Group
(TOGRU) CHAR/4 Bring values over as is.
LFB1 Credit Memo Terms
(GUZTE) CHAR/4 Bring values over as is.
LFB1 Chk. Double Inv.
(REPRF) CHAR/1 Bring values over as is.
LFB1 Chk. Cashing Time
(KULTG) DEC/3 Bring values over as is.
LFB1 Payment Methods
(ZWELS) CHAR/10 Refer to data mapping spreadsheet later in this spec.
LFB1 Alternate Payee
(LNRZB) CHAR/10 Bring values over as is.
LFB1 Individual Payment
(XPORE) CHAR/1 Bring values over as is.
LFB1 Bill of Exchange Limit
(WEBTR) CURR/13
Decimal/2 9999999999999.99 Bring values over as is.
LFB1 Payment Advance By EDI
(XEDIP) CHAR/1 Bring values over as is.
LFB1 Payment Block
(ZAHLS) CHAR/1 Bring values over as is.
LFB1 House Bank
(HBKID) CHAR/5 Not used. Do not bring forward existing values.
LFB1 Grouping Key
(ZGRUP) CHAR/2 Bring values over as is.
LFB1 Payment Method Supplement
(UZAWE) CHAR/2 Bring values over as is.
LFB1 Alternate Payee Indicator
(XLFZB) CHAR/1 Bring values over as is.
LFB1 Tolerance Group
(TOGRR) CHAR/4 Bring values over as is.
CORRESPONDENCE ACCOUNTING
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFB5 Dunning Procedure
(MAHNA) CHAR/4 Bring values over as is.
LFB5 Dunning Recipient
(LFRMA) CHAR/10 Bring values over as is.
LFB5 Last Dunned
(MADAT) DATS/8 Bring values over as is.
LFB5 Dunning Clerk
(BUSAB) CHAR/2 Bring values over as is.
LFB5 Dunning Block
(MANSP) CHAR/1 Bring values over as is.
LFB5 Legal Dunning Proceedings
(GMVDT) DATS/8 Bring values over as is.
LFB5 Dunning Level
(MAHNS) NUMC/1 Bring values over as is.
LFB1 Grouping Key
(MGRUP) CHAR/2 Bring values over as is.
LFB1 Local Processing
(XDEZV) CHAR/1 Bring values over as is.
LFB1 Acct. Clerk
(BUSAB) CHAR/2 Bring values over as is.
LFB1 Account with Vendor
(EIKTO) CHAR/12 Bring values over as is.
LFB1 Clerk at Vendor
(ZSABE) CHAR/15 Bring values over as is.
LFB1 Acct. Clk. Tel. No.
(TLFNS) CHAR/30 Bring values over as is.
LFB1 Clerks Fax
(TLFXS) CHAR/31 Bring values over as is.
LFB1 Clerks Internet
(INTAD) CHAR/130 Bring values over as is.
LFB1 Account Memo
(KVERM) CHAR/30 Bring values over as is.
PURCHASING DATA
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFM1 Order Currency
(WAERS) CUKY/5 Bring values over as is.
LFM1 Terms of Payment
(ZTERM) CHAR/4 Refer to data mapping spreadsheet later in this spec.
LFM1 Incoterms (Part 1)
(INCO1) CHAR/3 Refer to data mapping spreadsheet later in this spec.
LFM1 Incoterms (Part 2)
(INCO2)
CHAR/28 Bring values over as is.
LFM1 Minimum Order Value
(MINBW) CURR/13
Decimal/2 9999999999999.99 Bring values over as is.
LFM1 Schema group, vendor
(KALSK) CHAR/2 Bring values over as is.
LFM1 Pricing Date Cat.
(MEPRF) CHAR/1 Bring values over as is.
LFM1 Order Optim. Rest
(BOPNR) CHAR/4 Bring values over as is.
LFM1 Salesperson
(VERKF) CHAR/30 Bring values over as is.
LFM1 Telephone
(TELF1) CHAR/16 Bring values over as is.
LFM1 Acc. With Vendor
(EIKTO) CHAR/12 Bring values over as is.
LFM1 GR. Based Inv. Verif.
(WEBRE) CHAR/1 Bring values over as is.
LFM1 Auto.Eval. GR Setmt. Del.
(XERSY) CHAR/1 Bring values over as is.
LFM1 Auto.Eval. GR Setmt. Ret.
(XERSR) CHAR/1 Bring values over as is.
LFM1 Acknowledgement Reqd.
(KZABS) CHAR/1 Bring values over as is.
LFM1 Automatic Purchase Order
(KZAUT) CHAR/1 Bring values over as is.
LFM1 Subsequent Settlement
(BOLRE) CHAR/1 Bring values over as is.
LFM1 Subseq. Sett. Index
(BOIND) CHAR/1 Bring values over as is.
LFM1 B. Vol.Comp./Ag. Nec.
(UMSAE) CHAR/1 Bring values over as is.
LFM1 Doc. Index Active
(BLIND) CHAR/1 Bring values over as is.
LFM1 Returns Vendor
(KZRET) CHAR/1 Bring values over as is.
LFM1 Srv.-Based Inv. Ver.
(LEBRE) CHAR/1 Bring values over as is.
LFM1 ABC Indicator
(LFABC) CHAR/1 Bring values over as is.
LFM1 Mode Of Transport-Border
(EXPVZ) CHAR/1 Bring values over as is.
LFM1 Office of Entry
(ZOLLA) CHAR/6 Bring values over as is.
LFM1 Sort Criterion
(SKRIT) CHAR/1 Bring values over as is.
LFM1 PROACT Control Prof.
(PAPRF) CHAR/4 Bring values over as is.
LFM1 Revaluation Allowed
(XNBWY) CHAR/1 Bring values over as is.
LFM1 Grant Discount In Kind
(NRGEW) CHAR/1 Bring values over as is.
LFM1 Relevant for Price Determination
(PRFRE) CHAR/1 Bring values over as is.
LFM1 Relevant for Agency Business
(AGREL) CHAR/1 Bring values over as is.
LFM1 Shipping Conditions
(VSBED) CHAR/2 Bring values over as is.
LFM1 Purchasing Group
(EKGRP) CHAR/3 Bring values over as is.
LFM1 Planned Delivery Time
(PLIFZ) DEC/3 Bring values over as is.
LFM1 Confirmation Control
(BSTAE) CHAR/4 Bring values over as is.
LFM1 Unit of Measure Group
(MEGRU) CHAR/4 Bring values over as is.
LFM1 Rounding Profile
(RDPRF) CHAR/4 Bring values over as is.
LFM1 Price Marking Agreed
(LIPRE) CHAR/2 Bring values over as is.
LFM1 Rack jobbing service agreed
(LISER) CHAR/1 Bring values over as is.
LFM1 Order entry by vendor
(LIBES) CHAR/1 Bring values over as is.
LFM1 Serv. Level
(VENSL) DEC/4
Decimal/1 Bring values over as is.
PARTNER FUNCTIONS
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
WYT3 Partner Function
(PARVW) CHAR/2 Bring values over as is.
WRF02K Number (Partner)
(GPARN) CHAR/10 Map to new partner number in vendor correlation table.
ALTERNATE DATA
(Purchasing Data)
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFM2 Order Currency
(WAERS) CUKY/5 Bring values over as is.
LFM2 Terms of Payment
(ZTERM) CHAR/4 Refer to data mapping spreadsheet later in this spec.
LFM2 Incoterms (Part 1)
(INCO1) CHAR/3 Refer to data mapping spreadsheet later in this spec.
LFM2 Incoterms (Part 2)
(INCO2)
CHAR/28 Bring values over as is.
LFM2 Minimum Order Value
(MINBW) CURR/13
Decimal/2 Bring values over as is.
LFM2 Schema group, vendor
(KALSK) CHAR/2 Bring values over as is.
LFM2 Pricing Date Cat.
(MEPRF) CHAR/1 Bring values over as is.
LFM2 Order Optim. Rest
(BOPNR) CHAR/4 Bring values over as is.
LFM2 Salesperson
(VERKF) CHAR/30 Bring values over as is.
LFM2 Telephone
(TELF1) CHAR/16 Bring values over as is.
LFM2 Acc. With Vendor
(EIKTO) CHAR/12 Bring values over as is.
LFM2 GR. Based Inv. Verif.
(WEBRE) CHAR/1 Bring values over as is.
LFM2 Auto.Eval. GR Setmt. Del.
(XERSY) CHAR/1 Bring values over as is.
LFM2 Auto.Eval. GR Setmt. Ret.
(XERSR) CHAR/1 Bring values over as is.
LFM2 Acknowledgement Reqd.
(KZABS) CHAR/1 Bring values over as is.
LFM2 Automatic Purchase Order
(KZAUT) CHAR/1 Bring values over as is.
LFM2 Subsequent Settlement
(BOLRE) CHAR/1 Bring values over as is.
LFM2 Subseq. Sett. Index
(BOIND) CHAR/1 Bring values over as is.
LFM2 B. Vol.Comp./Ag. Nec.
(UMSAE) CHAR/1 Bring values over as is.
LFM2 Doc. Index Active
(BLIND) CHAR/1 Bring values over as is.
LFM2 Returns Vendor
(KZRET) CHAR/1 Bring values over as is.
LFM2 Srv.-Based Inv. Ver.
(LEBRE) CHAR/1 Bring values over as is.
LFM2 ABC Indicator
(LFABC) CHAR/1 Bring values over as is.
LFM2 Mode Of Transport-Border
(EXPVZ) CHAR/1 Bring values over as is.
LFM2 Office of Entry
(ZOLLA) CHAR/6 Bring values over as is.
LFM2 Sort Criterion
(SKRIT) CHAR/1 Bring values over as is.
LFM2 PROACT Control Prof.
(PAPRF) CHAR/4 Bring values over as is.
LFM2 Revaluation Allowed
(XNBWY) CHAR/1 Bring values over as is.
LFM2 Grant Discount In Kind
(NRGEW) CHAR/1 Bring values over as is.
LFM2 Relevant for Price Determination
(PRFRE) CHAR/1 Bring values over as is.
LFM2 Relevant for Agency Business
(AGREL) CHAR/1 Bring values over as is.
LFM2 Shipping Conditions
(VSBED) CHAR/2 Bring values over as is.
LFM2 Purchasing Group
(EKGRP) CHAR/3 Bring values over as is.
LFM2 Planned Delivery Time
(PLIFZ) DEC/3 Bring values over as is.
LFM2 Confirmation Control
(BSTAE) CHAR/4 Bring values over as is.
LFM2 Unit of Measure Group
(MEGRU) CHAR/4 Bring values over as is.
LFM2 Rounding Profile
(RDPRF) CHAR/4 Bring values over as is.
LFM2 Price Marking Agreed
(LIPRE) CHAR/2 Bring values over as is.
LFM2 Rack jobbing service agreed
(LISER) CHAR/1 Bring values over as is.
LFM2 Order entry by vendor
(LIBES) CHAR/1 Bring values over as is.
LFM2 Serv. Level
(VENSL) DEC/4
Decimal/1 Bring values over as is.
ALTERNATE DATA
(Partner Functions)
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
WYT3 Partner Function
(PARVW) CHAR/2 Bring values over as is.
WRF02K Number (Partner)
(GPARN) CHAR/10 Map to new partner number in vendor correlation table.Hi Shareen,
Have you looked Master Data Distribution (ALE) for Vendor since your legacy system are SAP?
Please check t/code BD14 (Send Vendor Master Data) and BD15 (Get Vendor Master Data).
Hope this will give you an idea.
Regards,
Ferry Lianto -
Hi
While creating purchase order for a particular material, system should take minimum order quantity.
For example, i create po 10ea minimum order quantity 25.then system should automatically should pick 25.
1)pls tell me where to define minimum order quantity?
2)is it work this scenario?
pls help me..........
thanksHi Bhaskar,
In materail master in the MRP1 Tab under Lot Size Data you have two options
Minimum Lot size and maximum lot size These two options would help you in determining the lot size when Placing a PO
setting the values in here will create a PO for minimum lot size Qty even if you give lessthan the qty specified in that field
In the same Material master Under Purchasing tab you have a check box Automatic PO flag this option as well
It Defines that purchase orders are generated automatically when purchase requsisitions are converted into purchase orders.
At the same time in the master record for the vendor with whom the material is ordered, the field "Automatic purchase order" must be flagged in the control data for the purchasing data.
Now PO's are generated automatically with the specified minimum order value
How ever this scenarion would be possible only if we are running MRP and finding material requirement and generating PR & PO automatically
I doubt it would work if you are creating PO manually
Hope this clarifies your doubt
Any further clarification required do put a message
If found useful reward accordingly
Thanks & regards
Pavan -
What credit limit is valid - the one set at Vendor master , PO or invoice ?
Dear Friends,
I want your suggestions, if weather there is any standard guidelines on which credit limit is followed if I maintain different values at Vendor master, purchase order and at Invoice level
Looking forward for your thoughts ?There is no credit limit for vendors, as we buy goods from vendor and not sell it to them
There are release strategies in MM. Please clarify your setup.
Regards,
Gaurav -
Process Sales Order based on minimum order
Hi Sap gurus,
Can any one Help me Out regarding How the System should have capability to process Sales Order based on minimum order quantity and minimum order value and How we will map In sap
Thanks
Points will rewards
Regards
RajeshHi,
We can set the control for Min order quantity in the Sales org1 view. Like wise we can control min order value also.
For that we have to use two condition types AMIW & AMIZ.
AMIW is min order value, where as AMIZ is min ord surcharge
Let's say AMIW value is 50,000.If the order value is less than 50,000 then AMIZ comes into picture.Amiz compares the automatically determined order value and AMIW value.The difference of those two values Amiz takes as surcharge and it overwrites the automatically determined order value with this value.
Like wise we can maintain min order value also by using this two cond types.
In the pricing procedure
subtotal req Altcal Altcond+bv
AMIW D
AMIZ 2 13
Award me points if u satisfy
Thanks,
Sudheer
Maybe you are looking for
-
Question about photo icons on songs.
Hey guys, I got a simple question to ask. Well, I just got a new 30GB Ipod Video today, and it works fine. However, after I added all of my songs to my ipod, I also wanted to upload the little photo icons next to them as well when you play a song. So
-
Character mode incompatibility.
Hi everybody, i had a problem while running a report. Rep-1219 occured during report execution. After looking in the help all we could manage to note was it is because of some character mode of creating the report. It also mentioned about the size of
-
How do I transfer InDesign app to my second home computer???
I have an IMAC with INdesign. I want to have the same INdesign App on my portable IBOOK. I tried to transfer the app from my IMAC to my IBOOK with a LACIE memory stick with no luck. Talked to a chap in India support for almost an hour with no luck.
-
Set up Yosemite on my iMac and MacBook Pro - no problems. Now I just discovered that Airdrop is completely dead on both. They cannot find each other. Had no problems whatsoever with Mavericks and cannot find any guide for solving this. Sharing is als
-
Please inform me why I am unable to convert my PDFs to Word Documents anymore. I've been signed up and paid forever now and no problems until today, Please inform me of what the problem is? Thanks bunches! :- @(