If you have created Vendor and Business partner separately they can be linked together. Please use transaction code FLBPC2 for this purpose. Ideally you should ensure that they have the same number which you can manage by maintaining the external numbering for one of them while creating differently.
Return Delivery for vendor consignment stock is not possible through SD deliveries.
While creating a return PO for Vendor Consignment stock, system comes out with the message ME 640 which is an error in standard SAP. However this message can be converted into a warning one to allow creation of the return PO.
Other methods for return will be (1) with 102 movement type in MIGO with reference to the original PO
(2) 122 movement against the GR document.
Outbound deliveries against Return PO is not possible.
Many times vendors keep supplying goods continuously to keep your business up and running. Prompt delivery is of utmost importance and price negotiation is a continuous activity which takes place in isolation with the deliveries. Vendor will keep on supplying you with a price agreed earlier. But one fine day your purchasing department will agrre to pay the vendor with a price which is effective from a past date i.e. price becomes effective retrospectively.
In such situations you use a standard SAP functionality called Revaluations which is executed through MRNB transaction. You use this function within Logistics Invoice Verification to determine the difference values on the basis of price changes that are retroactively valid and to create settlement documents for them. You can also revaluate purchasing document items for which you have entered invoices or credit memos in different currencies. You can send the revaluation settlement documents to the vendors as Messages or via EDI.
For Pre-requisites and method of carrying out this functionality please click here.
Standard SAP report MEIS does not bring the quantity into it normally.
For this to happen you must maintain “Special unit of Measure” in OVE1 transaction where you maintain the commodity code per country. In this, maintain the normal UOM as the Special UOM and run the report, it will populate the quantity in the item in MEIS report.
Config node: Materials Management –>Purchasing –>Foreign Trade/Customs–>Define commodity codes or import code number by country
Program MVER_DI is used to update hostorical consumption data for materials to get updated in table MVER or DVER.
For details please look at SAP Note 200547 – Program: Direct input for consumption values. You will find the MVER_WRITE_FILE in the correction instructions in this note.
Modify the program as per your requirement and upload the input file in special character format and give the logical file path of this file as input to the program MVER_DI.
The material consumption is generally only updated for the make-to-stock warehouse stock. By means of this consumption statistics you can forecast the future requirements and plan the material requirements according to the historic data.
However, such an MRP is not required for the sales order stock or Project stock since material requirements are planned requirements-based in this case. Therefore, an update of the consumption statistics for sales order stock and project stock is not desirable because consumption from these stocks would have an effect on MRP twice. Hence the system behaves as desired.
Reservations created automatically from PS, PP, MRP, CS, etc can not be deleted as it is possible for manually created Reservations. Such auto created reservations can only be deleted from the component which has created it. In most of the components, you can also set Final Issue Indicator which will will render the reservation in-effective. After this indicator is set from the source component, MBVR can delete it.
Example Reservations created from PS: In the Tab for procurement parameters (Proc.Param tab) Final Issue Indicator needs to be set to free the reservation created from PS.
You set a reservation with Deletion indicator if it is created manually, else if it is auto created, the deletion flag can be set from the application which created it (say PS, CS, etc) and then you use transaction MBVR (Manage Det er ingen tvil om at vi her har med et vaskekte og hoykvalitets casino pa nett a gjore, og det er bestandig morsomt a fa introdusere helnorske casinoer til vare lesere. Reservation) to delete the reservations. You also use this transaction to allow goods movement against a reservation.
For deletion, select the parameter “Set deletion indicator/delete”. The system will check whether all the items of a reservation can be deleted. This is the case if the requirement date of the reservation item is earlier than the date calculated from “base date – number of days”.
If the indicator “Only closed items” has been set, the reservation item must, in addition, either have been completely issued/withdrawn (quantity < = quantity withdrawn) or marked with the “final issue” indicator.
If all items of a reservation are marked as deleted, the entire reservation will be physically deleted. If this is not the case, those items that have fulfilled the deletion criteria will be marked with a deletion indicator. However, the reservation will remain in the system.
In case of Account Assignment objects, generation of Accounting document is controlled by the indicator “GR Non-Valuated” found in the Delivery Tab of the PO item. This indicator gets defaulted from the Account Assignment Object Configuration (OME9 Transaction).
For multiple account assignment till ECC EHP4, accounting entries were not allowed by SAP. From ECC EHP4 onwards, you can opt to generate accounting entries against the multiple account assignment byactivating the Business Function LOG_MM_MAA_1 in the transaction SFW5.
For Assets, the account Obtaining the highest free-credits-report.com score you can is simply a matter of good financial management. assignment object “A” by defauls comes with the indicator “GR Non-Valuated” as set (ticked). This gets defaulted in the PO. The actual value is not booked till the vendor”s invoice is posted and hence FI document is not generated. FI document gets generated when vendor”s invoice is posted at the time of MIRO.
If you are in SAP ECC, please type PDF! in the command prompt from the print preview screen and Press Enter. SAP converts the PO output to a PDF file which you can save in your system and mail it to the vendor.
This also can be achieved if you print preview from ME9F or SP01 using the spool request created.