PO Error No short text maintained in language ES - Short text in MM01

Question: I have a short text maintained in Material master in EN. The vendor master has a language set as ES( Spanish)

I logged in EN

When I try to create a PO i get a error "No short text maintained in language ES (please re-maintain material 106)" error number is ME095.

If I change the vendor lang to EN & maintain the ES lang in Material master, I am overcoming the error.

Can any one throw light on the importance of these texts & their effects.Vendor language is responsible for Po Prints I suppose & entry & display of text

Answer:
Basically, you need a communication strategy.
- What languages will you use to communicate to your vendor.
- Do not think theoretical, do it like it is done in real life.
- If you talk to your vendor in Spain, what language do you use?
- If you use English then put EN as communication langauge in your vendor master.
- You need to have material descriptions and many customizing settings available in the desired communication languages.

We usually use the local language for local vendors and English for all foreign vendors. If we have plants e.g. in Germany and Spain, then the spanish plants uses spanish for his local vendors and the german plant uses german language for the local vendors in Germany.

Both are using english for their foreign vendors. Shared vendors will have english too, as a german buyer is not able to talk in spanish or an spanish buyer is not able to talk in german language. Hence they would not know if it is accurate what will show up on a PO they create. They both can only validate the accuracy in a english written text.

Vendor language is responsible for PO Prints and I suppose also the entry and display of text. The language that SAP will be taken is from the Vendor language (Communication section) if I am not mistaken and this is the standard functionality of SAP. Of course, you can be able to manually change the language directly in the PO.

In the MM Purchasing component, a contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame.

Contracts are of two types:

1. Quantity contracts - Use this type of contract if the total quantity to be ordered during the validity period of the contract is
known in advance.

2. Value contracts - Use this type of contract if the total value of all release orders issued against the contract is not to exceed a certain predefined value.

But a scheduling agreement is a form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period. A scheduling agreement consists of a number of items, for each of which a procurement type is defined. The

The following are the procurement types:
- Standard
- Subcontracting
- Consignment
- Stock transfer

Delivery of the total quantity of material specified in a scheduling agreement item is spread over a certain period in a delivery schedule, consisting of lines indicating the individual quantities with their corresponding planned delivery dates.

SAP menu to create Contracts and Scheduling Agreement:-

Tips by : Manjunath

I have a Reqt wherein I should be able to know line itemwise the Materials Received(GR), Invoice Price and Qty Raised, Invoice to be Paid so that pending Qty and Amt can be calculated.

I will explain the scenario in Detail----

Say a PO has 3 Line Items A,B,C of 10 Quantities each has been ordered to a vendor.

Out of which for Item A---------All the 10 Nos have been delivered.
For Item B-----------5 Nos have been delivered.
For Item C, Nothing has been delivered.
So Invoice(MIRO)has been posted for 10, 5, 0 Nos for the three Items.

In FI side, is there any transaction code where in we can go and see Line Item display of which material---------how much is the PO Qty, GR Qty, Invoice Qty and the Invoice Amt to be paid individually line itemwise?

In F.13 we could see the consolidated amt for each vendor but we want the PO Line Itemwise Qties delivered and payment amt so that the remaining Qty and Amt can be calculated.

Goto Transaction MB5S - List of GR/IR Balances

Fill in the mandatory inputs and check the result list.

Tips by : Ramesh

In the movement type config - there is an auto PO creation flag, which allows the system to automatically create PO in the background from within the GR posting transaction. Has anyone used this feature -please share your experience. We are on 46c, and I don't see any existing movement type in the system which has this flag turned on.

For business process control purpose, I suggest avoiding auto PO from GR unless it is really necessary. Instead, use "traditional" PR-PO-GR process.

Actually what is the rational of using a automatic PO function, what is the benefit and what is the disadvantages of using this function? and under what business practise is best suit to use this function?

Sometimes the SAP help portal give you a lot of technical but didn't explain thoroughly from the business perspective point of view.

One of the benefits of using this feature is that you are taking delivery of the raw materials which are delivered by trucks and since it is not possible to capture the actual receipted quantity at the time of PO creation. Other benefits is to reduce the workload of purchasing department for the case of consignment process.

How to create AUTO PO during MIGO ?

Check in customizing whether you have maintained creation of automatic PO during good receipt.
Menu path : MM -> Inventory Management -> Goods Receipt -> Create Purchase order Automatically -> Activate Auto PO creation for Mvt type.

And then activate Auto PO creation in vendor master.

I am facing problem in GR creation for Schedule agreement. When I am creating GR, it is telling no items exists even though Schedule agreement & schedule lines maintain for that. Some times when they are many lines and if we do GR for one line automatically all lines disapper and won't come stock or don't show in schedule lines.
I am in 4.7 version.

Please check whether you have attached SA in the source list with line items.

The following are the steps in 4.6B.

T-code:ME01
Enter Mat.code & Plant.
In the next screen pl.do the following:

Valid from - commencement date of the SA
Valid to - End date of the SA
Vendor - Vendor on whom the SA is released
POrg - Your purchase organisation
PPL - Leave it blank(This is only for interplant)
OUn - Ordering unit
Agreement - SA number
Item - 1
MRP - 2 - Record relevant to MRP, Schedule line generated automatically

If you are having several items in one SA,you have to do the above repeatedly by giving the 'Item'1,2,3 etc.in each line.
Then run MRP.You will have the sch.lines and you can receive the materials without any problem.

If you have already done the MRP, pl.maintain the sch.lines in ME38 by selecting each items.

K.Annamalai.

I'm struck at creating the Purch Organisation at Client level for the client purcahses. The purchasings are done at the client (Group of company level). could any one let me know how tocreate the Purchasing Org at client level.

The Purchasing Org at the client level is called Reference Purchasing Org. create a Purchasing Org and assign all the Pur Org to this Purchasing Org.

This again depends on the requirement.......precisely tell me what is your requirement?

Sumit

Ref Pur Org is not for the client level purchases dear. Can you raise the PO with ref Pur Org. If at all you try to raise what plant give in PO as with out plant you cannot create PO.
My requirement is to create corporate purchases with a corporate Pur Org without mentioning plant at the PO level. I guess fico won't be having any problems with the accounting & valuaion. Eg: Tata Group wishes 2 purchase one lakh of computers for all its company codes in all the parts of word with a singlw PO with out mentining plant in the PO.

P Rao

Ref Purchasing Org creates Contract and it is at the corporate/client level. Now, that contract is used by the respective Pur Org at the Company Code level.

Now if you want to procure Computers for all the company code then you can do that like this:

Suppose you have plants 1, 2,3,4. and company code a,b,c,d. Pur Org you have P1, P2, P3 and P4.

Assign 1 to a, 2 to b, 3 to c and 4 to d. one plant has to be assigned to one company code.

Now in PO, plant comes in the item level, that means you have to buy the material for a plant which belongs to a company code.

Now you can assign one or more plants to one pur org. like 1 and 2 to P1, 3 to P2 and 4 to P3 and 1,2,3,4 to P4.

Now don't assign pur org P4 to any company code. that means P4 can procure for all plants across all company code.

Now you can raise a PO for all company code through P4. But this can be done for respective plants.

Now you can create another Pur Org P5 and assign p1 to P4 to P5. and keep a contract at P5. That means the contract can be used by any Pur org to procure computers for respective plants.

Sumit

Now don't assign pur org P4 to any company code. that means P4 can procure for all plants across all company code.

but in this secnario, if I raise PO I have to give the data of company code in PO. which company code will put here. also how the GL acounts are updated by the purchases as it belongs to the entire client but not the comapny codes.

P Rao

You want to purchase across all Company code that is correct.

But how can you purchase without company code. You have to give it.

Max you can do, you can create a virtual Plant and consolidate all the requirements there and raise a PO from that Plant and Company code and receive it at the same plant and Transfer the material to the company codes.

But, you have to define the vendor and material at the virtual plant. In that way, you can take care of the vendor payment and proper account posting. Account posting cannot be done at the client level.

I hope this helps.

Sumit

Tested in 4.6c

To see the components button tree display.

Create a default variant.

Called transaction MIGO_GR again. You must see a Line column before the components columns can be display.

If you want the system to take the price from the last Purchase Order, then do not maintain the conditions in the info record because it has precedence over the last PO. This means that the netprice field in the info record should be left blank.

In the case when you have already maintained the conditions in the info record (or netprice), try to delete them or make them invalid by changing the validity date.

Even though no price was maintained, the info record will still keep track of the Order price history.

To check the Order price history, go into the material info record and click Environment -> Order price history

Finally, check your PO Release Strategy configuration to make sure that there are no errors.

OMGSCK - Check Release Strategies
(make sure there are no error messages)

Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.

Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.

In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.

The person with the release authorization have to use ME28 to release the Purchase Order.

OMGS - Define Release Procedure for Purchase Order Type

Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Save your entries.

Release codes - New entries
Grp Code
02 01
Save your entries.

Release indicators - New entries
Release indicators Release Description
0 Blocked
1 X Release
Save your entries

Release Strategy - New entries
Release group 02

Rel.strategy 01 - Release

Release codes 01

Release status 0 - Blocked
1 - Release

Click the Release prerequisities button

Click the Relase statuses button the click the Continue button

Click the Classification button

Choose your check values

Click the Back button

Save your entries

Transaction code : CL02 - Class

• Class - Create REL_PUR
• Class type - 032
• Click Create button
• Description - Release Procedure for Purchase Order
• In the Same Classification section, click Check with error
• In the Char. (characteristic) tabstrips, type NETVALUE to assign your characteristics to the class
• Save your data and this message will appear :-

Class type 032: Class REL_PUR created

Transaction code : CT04 - Create Characteristic e.g. NETVALUE

• Click Additional data tabstrips
• Table name CEKKO Field name GNETW and press enter and you will see this information message :-

Format data taken from Data Dictionary (press enter)
• (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
• In the Basic data tabsritps (X refers to tick),

X Mutliple values
X Interval values
• In the Value data, in the Char. value column, type >=10000 (equal or greater than 10000) and press enter
• Save your data

4.6x

The aim of the sap purchase order release procedure is to replace the manual written authorization procedures. An electronic signatures is used instead, maintaining the dual control principle. The person responsible for the processes of the requisition or other purchasing document in the system have to approve by marking an "electronic signature" which can give the document legal force for further processing.

Briefly, this is how the purchase order release strategy works :-

The release code is a two character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).

Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.

An example of configuring a Purchase Order Release Strategy :-

If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.

Steps for configuring the PO release strategy :-

1. Create the PO Characteristic
2. Create the Class of the PO Release Strategy
3. Define the Release Procedure
4. Check your PO release configuration

There are some fields which you can set as defaults for the buyer in transaction ME21.

Transaction SU01
Input the user name and click Parameters

PID Parameter value
LIF - Vendor number
BES - Purchase Order Number
BSA - Order type
EKG - Purchasing group
EKO - Purchasing organization
WRK - Plant
LAG - Storage location
MKL - Material group
WAK - Promotion

Create a new message types for a different layout of Purchase Order

• M/34 - Maintain message types
• Click the Partner definition button
• Insert the new message type to the Partner
• OMQN - Fined-tuned Message Control
• Add a new Printer Operation 1 - New 2 - Change
• OMFE - Layout sets for Purchase Order
• Attach the new message type to the new layout sets
• M/36 - Maintain message detemination schema : Purchase Order
• OMQS - Assign schema to Purchase Order
• OMGF - Assign Output devices to Purchasing Groups
• MN05 - Assign default Message Type to Purchasing Groups

In the SAP standard info structure S012 is updated by the Purchase Order creation date, not the Goods Receipt date. e.g. a Purchase Order is created in January and good receipt is in February and March, S012 will shows the values in period January.

• Transaction MC26
• Info structure S012 Update group (stats) SAP
• Double click on Goods received qty
• In the section Date field for period determination

Automatic Discount for Vendor when creating Purchase Order

• Transaction M/06
• Double click on the Discount Condition you want to set e.g. R003
• In the Access Sequence type 0006 - Vendor Discount
• Save it and goto Transaction MEKE
• Enter the Vendor code you want to set and click execute
• Put your cursor on the Vendor Code and click Create
• Type in the Discount Rate and save it
• for larger vendor discount for larger quantity, click the Scales button

If you create your own condition table, you will not be able to use the standard transaction found in the menu Purchasing -> Master data -> Conditions (excluding Other). Instead, you used the transaction MEK1 (Other Condition) to maintain your condition type.

e.g. Transaction MEKE points to the program RM06K023

• In the program RM06K023, double click on the module SAPFM06K
• Click Edit -> Search/replace, type in 044 (condition table for vendor)
• Tick in program SAPFM06K

You can see that SAP hardcoded the standard condition table for the standard transaction found in the menu Purchasing -> Master data -> Conditions (excluding Other)

Suppose you want to calculate the GST and DISCOUNT for a Net Value of 1000.
Net value 1000
GST 10% of 1000 100
DISCOUNT 10% of 1000 100

Final Net value 900

This is what you do :-

• M/08 - Define calculation schema
• First check the conditions column Steps e.g. PB00 and PBXX belongs to step 1.
• Next check the last Steps after Actual Price
• Now, look at the column Fro To
• If you want the DISCOUNT to be calculated based on 1000, put the Steps number in the column Fro

The Fro To controls the calculation.

Transaction OMFI

• Double click on the default values you want to change.
• Save it.
• Next, you've got to associate via SU01
• Click Parameters, insert a new parameter id EVO to the authorization code.
• Type in Parameters value you want e.g. 01
• You have to assign the control for ALL the SAP buyers via thier SAP users id.
• Logoff and login again. Then try to create a Purchase Order and check the default values.

In the Fast Processing button :-

• you can choose whether to adopt automatically all the line items fields in the Purchaes Requisitions.

Transaction OMET

• Create a new entry, give it a name and tick :-
• Ref. to PReq
• Ref. to P.O.
• Ref. to quotation
• Next, you've got to associate via SU01
• Click Parameters, insert a new parameter id EFB to the authorization code.
• Type in Parameters value you want e.g. XX
• You have to assign the control for ALL the SAP buyers via thier SAP users id.
• Logoff and login again. Then try to create a Purchase Order without a reference.