Unable To Create PO Due To Language Error

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.

Item Wise Display of Invoice Amt to be Paid to Vendor

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.

Auto PO creation During GR Posting

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.

GR Creation for Schedule Agreement

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.

Purchasing Organization at Client level

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.

Where to find the MIGO_GR Components button?

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.

Prompt the last Purchase Order Price for the Material

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

Configuring the PO Release Strategy

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

User Defaults for Purchase Order

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

Configurable Materials in SAP Purchasing

Purpose

You can use variant configuration for purchasing materials. This means that the material is procured externally, rather than produced in-house.

Restrictions

• You cannot configure a material in the purchase order itself.
You can only configure a material when you create a sales order. If you need to procure your material externally, the characteristic values assigned to the material are copied to the purchase order. You cannot change the configuration of the material in the purchase order.
• If the characteristic values in the sales order are changed, the values in the purchase order are changed accordingly.
However, these changes are not marked.

Process Flow

1. Create a sales order containing a configurable material that is procured externally.
The material need not have a BOM. However, the material must have a configuration profile with an allocation to a class. The characteristics of the class are used to describe the material.

Your externally procured material may be part of a BOM. Depending on the BOM explosion settings in the configuration profile, the material may be configured either independently or according to the characteristic values assigned to the BOM header material.

2. A purchase requisition can be generated either in the sales order itself or as a result of a material requirements planning (MRP) run.
The purchase requisition contains the characteristic values that were assigned to the material in the sales order.
3. The purchase requisition is converted to a purchase order.
The purchase order contains the characteristic values that were assigned to the material in the sales order. When you print the purchase order, these characteristic values are printed with it.

See also:

Variant Conditions in Purchasing

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Archiving SAP Purchase Orders

Use

Your system administrator archives inactive POs periodically. Archived documents are removed from the database.

For detailed information on archiving purchasing documents, refer to the documentation CA Archiving Application Data (section on MM Materials Management).

When is a PO Deactivated?

A purchase order is deactivated when all of its items meet one of the following criteria:

• Item has been cancelled
• Order quantity (or more) has been delivered and invoiced
• Delivery completed indicator has been set and the invoiced quantity is greater than or equal to the order quantity

By making the appropriate system settings, you can specify that PO items cannot be archived if they are listed in a purchasing info record as belonging to the most recent PO in the system (that is to say, if they are liable to serve as a source of default data).

Activities

Purchase orders are archived in two phases:

1. Deactivation: All PO items meeting one of the above criteria are given the status Deactivated.
2. Archiving: The deactivated POs are deleted from the system and archived in a separate storage medium.

In the same way as other purchasing documents, deactivated POs remain in the system until they have been archived by your system administrator. The latter initiates the archiving process for purchase orders via Purchase order ® Follow-on functions ® Archive.

You can list documents that have been archived as follows: Purchase order ® Reporting ® Archived purchasing documents.

This database-oriented archiving must be distinguished from document archiving in optical archiving systems by means of SAP ArchiveLink. If ArchiveLink is used and the appropriate settings are made in ArchiveLink Customizing and Message Customizing in Purchasing, purchase orders that are outputted as messages can be optically archived. You can view optically archived purchase orders from within the SAP document display via Environment ® Display originals.

For more detailed information, refer to the section Optical Archiving of Outgoing Purchasing Documents in the documentation SAP ArchiveLink - MM Document Storage Scenarios.

For more information on SAP ArchiveLink, see BC - SAP ArchiveLink - Application Scenarios.

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Monitoring SAP Purchase Orders

Displaying a Purchase Order

1. Choose Purchase order
® Display.
2. Enter the PO number.
3. Press
ENTER. The item overview for the chosen PO appears.

Displaying PO Header Statistics

The PO header statistics show information pertaining to the entire document (for example, the total goods receipt value and the total invoice value).

To display these statistics, choose Header ® Statistics ® General.

Displaying Statistical Data on an Item

Choose Item ® Statistics ® General to display statistical information on the status of individual PO items.

Displaying the PO History

The purchase order history is actually a history of all the transactions that have occurred with regard to a PO item to date (for example goods and invoice receipts relating to the item, incurrance of delivery costs, down-payments, and so on).

To display the PO history, select the item and choose Item ® Statistics ® PO history.

Views of the PO History

When displaying the order history, you can switch between different views. In this way, you can display the following information:

• Invoices received and their clearing value
• Quantity in "blocked stock"
• Delivery costs
• Assignment of GR and IR documents in the case of items subject to GR-based invoice verification

To switch between views, choose Views.

Analyses of Purchase Orders

You can run reports analyzing Pos according to a variety of criteria. A number of different analyses are available in the system:

Listing by

• Range of material numbers
• Purchasing group
• Requirement tracking number
• Material group

Account assignment
Listing of purchase orders for a given account assignment (for example, by cost center).

Order value analysis
Allows you to create your own ABC analysis of purchase orders. You can classify orders by order value, average value per order, and number of orders.

PO number
Listing of all purchase orders within a range of numbers.

Archived purchasing documents
Listing of Pos that have been removed from the system and archived.

Requirement tracking number
Listing of all purchasing documents created with reference to a series of purchase requisitions having a certain requirement tracking number. The analysis shows the requisitions for which purchase orders have already been created.

Vendor/material
Listing of purchase orders created for a particular vendor, material, or material group.

For more information, refer to the section Reporting in Purchasing.

For general information on reporting and analysis functions in the R/3 system, see the documentation Getting Started with the R/3 System.

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Blocking a SAP Purchase Order

You block a purchase order item to prevent a goods receipt involving the relevant material.

Prerequisites

You can only block those items with respect to which no goods or invoices have yet been received.

Procedure

1. Choose Purchase order
® Change.

The initial screen appears.

2. Enter the number of the purchase order you wish to block. Press
ENTER. The item overview screen appears.
3. Select the item you wish to block. Then choose Edit
® Block.

The system inserts an S in column D of the item.

To unblock the item, select it on the item overview screen. Then choose Edit ® Reset deletion ind.

4. Save the purchase order.

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Cancelling a SAP Purchase Order

If you have ordered 100 units of a product in a purchase order item, but after taking delivery of 25 of these you no longer wish to have the remainder, you cancel the PO item.

Procedure

1. Choose Purchase order
® Change.

The initial screen appears.

2. Branch to the item overview.

There are two possible situations:

Situation	You
The invoiced quantity (IR, or invoice receipt, quantity) is equal to the goods receipt (GR) quantity	Select the relevant item then choose Edit ® Delete. If appropriate, reduce the order quantity in the PO for statistical purposes.
The IR quantity is not equal to the GR quantity	Reduce the order quantity in the PO.

1. Save the document.

Result

The purchase order is created in the R/3 System. In order that the information from the PO can be transmitted to the vendor, the system generates a message for the PO. How to transmit the message to the vendor is described under Outputting Messages.

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Changing a SAP Purchase Order

1. Choose Purchase order
® Change.

The initial screen appears.

2. Specify the number of the PO to be changed and press
ENTER.

The item overview screen appears.

3. Change the PO as desired.

– Adding items: To add a new item (if the screen page is full), choose Edit ® Enter lines.

– Changing items: If the desired changes are not possible on the item overview screen, select the relevant item and choose Item ® Details.

– Deleting items: Select the items you wish to delete. Then choose Edit ® Delete.

4. Save the purchase order.

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Changing, Cancelling, and Blocking SAP Purchase Orders

Use

You can change, cancel, and block purchase orders.

Prerequisites

Note the following points:

• Has the PO already been sent to the vendor?

If you change a PO after it has been sent to the vendor, a change document (change notice) is generated and sent to the vendor. This tells the vendor what you have changed.

• Has the vendor delivered - in full or in part - the materials covered by the PO item(s) you wish to change?

If the goods have already been delivered, then the changes you can make to the PO are limited. For example, you cannot change the quantity to one that is less than the quantity delivered.

• Has the invoice already been received or have the goods already been paid for?

If the invoice has been received or the goods have been paid for, and your intended change affects the price, the change will be ineffective.

You can display the PO history for an item to determine whether deliveries have been received or the item has been invoiced.

See also:

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Generating Further SAP Invoicing Plan Dates

If you have assigned a periodic invoicing plan to a PO item but have not initially defined invoicing dates covering the entire validity period of the purchase order, you can generate further dates in due course.

You have created a PO item with a periodic invoicing plan for a certain planned procurement. The purchase order is valid from 1.1. to 12.31. When creating the invoicing plan, you specified one invoicing date per month for the first half of the year. You have not yet planned any dates for the second half of the year because you do not wish information from the invoicing plan to be passed on to purchase order commitments at this stage, for example.

By mid-June, it is clear that the PO is to proceed as envisaged, and you therefore wish to schedule invoicing dates for the remainder of its validity period.

Procedure

To schedule further invoicing dates, proceed as follows:

1. Choose Purchase order ® Follow-on functions ® Period. invoicing plan
2. Specify the purchase orders for which invoicing dates are to be generated in the invoicing plan and perform the function.

A log can be created if desired.

Result

The system adds further dates on the basis of information such as the validity period or horizon from Customizing, the purchase order, and the invoicing plan.

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

Settlement of Amounts Due Under SAP Invoicing Plans

Automatic Settlement Accounting

As a rule, automatic settlement accounting is used in connection with periodic invoicing plans.

You can have invoices generated in the system and forwarded to Financial Accounting for payment automatically with respect to PO items for which you have scheduled a series of invoicing dates in an invoicing plan.

If you have several PO items with invoicing plans in the system (usually providing for invoicing on different dates), it is advisable to carry out settlement accounting with regard to these plans on a daily basis.

Manual Invoice Creation

You have to create invoices manually in connection with partial invoicing plans if you have no reference invoicing plan for the system to use as a basis for generating suggested invoicing dates for the plan in question.

Please refer to the Logistics Invoice Verification documentation for details.

Procedure

To carry out automatic settlement accounting with respect to invoicing plans, proceed as follows:

1. Choose Logistics ® Materials management ® Invoice verification ® Logistics invoice verification.

2. Choose Further processing ® Invoicing plan.

On the initial screen, enter your selection criteria for the invoicing plans in respect of which settlement is due.

3. Start the settlement accounting process either online or in the background.

You can set the Test mode indicator in order to initially simulate the results of settlement accounting.

After running the settlement accounting program, you get a log listing the invoiced transactions and drawing your attention to any errors that may have occurred.

Result

You have invoices in the system, which are processed further in Financial Accounting.

• Configurable Materials in SAP Purchasing
• Archiving SAP Purchase Orders
• Monitoring SAP Purchase Orders
• Blocking a SAP Purchase Order
• Cancelling a SAP Purchase Order
• Changing a SAP Purchase Order
• Changing, Cancelling, and Blocking SAP Purchase Or...
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP

SAP Purchase Orders Invoicing Plan

Use

The invoicing plan is a facility that allows you to schedule desired invoicing dates for planned procurements independently of the receipt of the relevant goods or services. It lists the dates on which you wish to create and then pay the invoices in question.

You do not wait each time for the vendor to submit an invoice for goods supplied or services performed, but can have invoices created automatically by the system on the basis of the data available in the purchase order and then release them for payment to the vendor.

The following two types of invoicing plan are available:

• Periodic invoicing plan
• Partial invoicing plan

Periodic Invoicing Plan

The periodic invoicing plan can be used for regularly recurring procurement transactions (e.g. rental, leasing, or subscriptions).

It facilitates the largely automatic creation and payment of invoices within the framework of the invoice verification process. The periodic invoicing plan uses evaluated receipt settlement (ERS) program functionality.

In the case of the periodic invoicing plan, the total value of the PO item is invoiced on each due date.

A monthly sum of $600 is charged for a leased car (represented by an item of a PO). This sum is invoiced and paid on the last day but one of each month.

In Customizing for Purchasing, you can define whether the dates are to be maintained manually or whether the system is to suggest invoicing dates according to the specified rules.

Partial Invoicing Plan

The partial invoicing plan can be used for the invoicing of high-cost material or projects involving the procurement of external services that are to be subject to stage payments (such as plant construction projects, or the invoicing of individual stages of a building project following completion in each case).

You can also flag due dates in a partial invoicing plan as dates for advance payments.
The amounts corresponding to these dates are then not taken into account in the sum total of the invoice items because advance payments are set off against later invoices.

In the case of the partial invoicing plan, the total value of the PO item is broken down and spread over the individual dates of the invoicing plan.

A purchase order item relates to building project no. 1 with a total value of $900,000. 33.3% ($300,000) of the total value is due to be invoiced and paid on completion of the first phase of construction, a further 33.3% ($300,000) on completion of the second phase, and the rest ($300,000) following completion and acceptance of the 3rd and final phase.

In the partial invoicing plan, you wish to maintain the invoicing dates agreed with the vendor yourself. Therefore there is no system support in the form of date proposals.
However, if you wish to have due dates suggested by the system as an entry aid, you can reference an existing plan when creating a new invoicing plan. Date proposals can then be adopted from the former.

Integration

When you save the invoicing plan, data is passed on to purchase order commitments, cash management and cash forecast.

Prerequisites

To be able to work with invoicing plans:

• You must maintain the settings in Customizing for Purchasing, e.g.:

- Invoicing plan type

- Date categories

- Date descriptions

- Date proposals

• The PO item must have account assignment
• You must use Logistics Invoice Verification

If you wish to use automatic settlement for periodic invoicing plans, automatic invoice creation must be agreed with your vendor. Eval. receipt sett. must be selected in the vendor master record.

SAP recommends working with the order type FO.

An extended validity period and a "reason for cancellation" are defined in the header of this type of purchase order. The specified validity period is adopted for the invoicing plan.

If you work with standard purchase orders, you must maintain the date determination rules accordingly in Customizing, since there is no predefined validity period that can be adopted in the invoicing plan.

• 
  
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP
• SAP Purchase Orders Invoicing Plan
• SAP Purchase Order Returns to Vendor and Store Ret...
• SAP MM Returns
• Materials Subject to Split Valuation SAP Purchase ...
• Goods-Receipt-Based Invoice Verification
• Specifying Incoterms and Purchase Orders Shipping/...
• Incoterms and SAP Purchase Orders Shipping/Deliver...

SAP Purchase Order Returns to Vendor and Store Returns

Use

The reasons for returns to vendor and store returns include:

• Goods remain at the end of a promotion
• Goods remain at the end of a season
• The vendor asks for the merchandise to be returned
• Goods have to be returned/destroyed because they are spoiled, broken or of inferior quality
• Articles are being discontinued
• The merchandise involves empties or returnable transport packaging

Features

You can mark articles to be returned when you are entering an item in a purchase order by selecting the R indicator (returns item) on the item overview screen of the purchase order.

Returns order items can be entered in a purchase order alongside other order items. This enables you to order goods from and return goods to a vendor in the same purchase order.

Returns to vendor can be managed completely on the procurement side: They leave the site at the receiving dock (i.e. when the vendor makes a delivery) and the relevant items are handled as negative values in Invoice Verification.

Activities

If you require shipping documents or freight lists for the return, you also have the option of using the shipping processing functionality.

• 
  
• Generating Further SAP Invoicing Plan Dates
• Settlement of Amounts Due Under SAP Invoicing Plan...
• Creating an Invoicing Plan in SAP
• SAP Purchase Orders Invoicing Plan
• SAP Purchase Order Returns to Vendor and Store Ret...
• SAP MM Returns
• Materials Subject to Split Valuation SAP Purchase ...
• Goods-Receipt-Based Invoice Verification
• Specifying Incoterms and Purchase Orders Shipping/...
• Incoterms and SAP Purchase Orders Shipping/Deliver...