Mm Tickets.docx

#Incident: 11 You are using Official document numbering functionality and trying to post MM invoice for Italian company code, the system takes a long time to post an invoice. This performance issue caused due to the note 1756401 corrections.

Reason and Prerequisites Reason: Program error. Prerequisites: You must have implemented the note 1756401 along with its prerequisite notes. Solution Implement the correction instructions relevant for you release. After implementing the note corrections, performance issue caused while posting an MM invoice will be resolved.

#Incident:12 Symptom You are applying a correction that requires some of the corrections included in this note. Other Terms GTAS, Material Management, MM, ME31, scheduling agreements Reason and Prerequisites Reason: Legal Requirement The corrections in this note are intended to provide an interface in the Material Management for a logic that includes USFG fields when creating Scheduling Agreements. Solution Import the relevant support package, or implement the attached correction instructions.

#Incident:13 Tax Code Automatic Determination, MM, IVA, tax code determination,

Reason and Prerequisites This note is relevant only for Brazil. You have implemented Note 1894759. All Tax Code Determination MM features are activated by: o Business Function: LOG_TMF_INT_1 - Switch: ITMF_SFW_MM_TC Solution Changes were made to make the IVA automatic determination consistent on MEK1 transaction. As a general rule, SAP recommends that you install a solution by applying a Support Package. However, if you need to install a solution earlier, use the Note Assistant to implement the correction instruction. You can find more information about the Note Assistant in SAP Service Marketplace, under service.sap.com/note-assistant. Note that documentation, transactions, and Customizing activities are only delivered via Support Package. To implement the solution, you must carry out manual activities and implement the correction instructions that are valid for your release.

#Incident:14 Difficult to find relevant notes to correct ZH translation errors Reason and Prerequisites Grouping Chinese translation relevant notes by application area Solution This note serves as the collective note for all Simplified Chinese translation issue relevant notes relating to application MM (Material Management) access to all different existing notes to address ZH translation issues (translation error and/or missing translation). You can follow below procedure to find the notes created to address ZH translation issues to your

applications. 1.Implement the notes in the Related Notes area manually according to the instruction contained in them or implement the support package if it's indicated at the bottom of the note in question. Note: Please check the Software Component and Releases at the bottom of each note to check if it's applicable to your system.

#Incident:15 Error message G4042 in intercompany posting with transaction MIRO Reason and Prerequisites The error occurs after note 542301 was installed. Solution see program change

#Incident:16 Posting an MM invoice against a GR item with VAT causes the above error due to the JV document not balancing. The error occurs in routine CHECK_MM_JV_DOC (LGJVIF30). The table bal_sum has a balance as it contains two lines eg 235.00 for vendor line, 200.00 for GR/IR line. The difference is the VAT amount. This error appears to have started after implementing note 83818 to solve a problem with splitting of VAT on downpayments.

Reason and Prerequisites The change made with note 83818 should only apply to FI clearing documents. It was not checked, that it does not apply to MM. Solution see changed note 83818

#Incident:17 After implementing note 1545441, it is possible to change the annexing package subscreen field. However, the chage disappears in any click and cannot be saved. Solution Implement the source corrections will fix the symptom mentioned above.

#Incident:18 Indian Union Budget 2010 - 2011 will be announced on 26/02/2010. This is the master note for communicating to customers any legal changes which are announced in the Budget 2010 related to the Logistics processes (MM and SD). This note will be updated on a regular basis with information regarding any notes being released for budget 2010 - 2011 and customers are encouraged to check this note for any announcements from SAP. In addition, this note also contains details of the minimum SP level customers must be on to obtain support in the event of a legal change. This Note also provides information on the following topics: i) Where will we find the corrections delivered by SAP to incorporate the new legal change? ii) In case of queries related to the Budget, is there any contact numbers at which I can reach SAP? This Note also provides information about few Frequently asked questions asked by customers in the event of existing tax rates being changed/enabling existing tax functionality: i) How should a change in tax rate for an existing excise duty be handled in MM? ii) How should a change in tax rate for an exisiting excise duty be handled in SD? iii) How to handle open import process POs? iv) How to handle Service tax rate changes? v) How to handle excise rate determination based on GR date? vi) How are excise duties and other taxes determined in case of new rates in MIRO transaction? vii) Information on Customizing Notes and service tax related solutions for Customers who will be under the Service tax regime as part of Budget 2010.

Solution I. Preparatory Activity: 1. Ensure you are on the minimum support pack level required for your SAP release in order to obtain support from SAP in the event of a legal change announcement. The details of the mininum SP level required can be found in the note 1175384. II. Frequently asked questions: 1. Frequently asked questions by customers in the event of a new tax / cess being introduced in the budget i) Where will we find the corrections delivered by SAP to incorporate the new legal change? Ans: This master note will be updated regularly with the list of notes being released for the legal change. Customers are requested to check for this master note on a regular basis for information on the Indian Budget 2010 - 2011. ii) In case of queries related to the Budget, is there any contact numbers at which I can reach SAP? Ans: Customers can contact SAP at the hotline phone numbers which are dedicated to customer queries on the Indian Budget for 2010: +91 80 4139 9150 +91 80 4139 8573 These numbers will be active from 9am to 6pm IST. 2. In case of change in rate of an existing tax, customers would need to carry out the necessary changes in customizing to incorporate this change.

Frequently asked questions by customers in the event of existing tax rates being changed -

i) How should a change in tax rate for an existing excise duty be handled in MM? Ans: For Customers using TAXINN - Create a new conditions records starting from date of changed rates with new rates. For Customer using TAXINJ - Maintain the new tax rate in J1ID with the new validity period starting from the date from which the rates have changed.

ii) How should a change in tax rate for an existing excise duty be handled in SD? Ans: For Customer Using TAXINN - Create a new condition record with revised rate & the validity should start from the date from which the rates have changed. The Pricing type of the Item category should be changed to 'C' in the Delivery to Billing or Order to Billing copying Control (VTFL -> Delivery related billing, VTFA -> Order related billing). This customizing changes will get the new rates during billing for all the old open Sales documents. For Customer using TAXINJ - Change the existing tax code and maintain Excise duty rate in J1ID with validity starting from the date from which the rates are changed.

iii) How to handle open import process POs? Ans: We recommend to close the open POs for which the goods receipt process is complete. Else if the POs are to be kept ope then the existing lines should be closed and new lines can be added for which the changes introduced will be applicable and this will not affect the closed lines in the PO.

iv) How to handle Service tax rate changes? Ans: If there is any rate change in Service tax: It is mandatory to create a new tax code for customers using Deferred tax code. For customers not using Deferred tax solution for service tax, consider pre-closing the LIV & then change the tax rate instead of creating a new tax codes. For SD, customer can change the tax rate in the existing tax codes / Condition records.

v) How to handle excise rate determination based on GR date? Ans: Refer to the following notes to consider Goods receipt(GR) date to determine excise rates. NOTE 1147512 - For considering GR date for excise rate determination in J1IEX. NOTE 1150781 - For picking excise rate based on GR date in MIGO for depot.

vi) How are excise duties and other taxes determined in case of new rates in MIRO transaction? Ans:The excise duties are defaulted with the values captured in excise invoice. Other taxes such as VAT, sales tax and service tax are determined on the posting date of the Invoice. In scenarios where the Invoice needs to be posted with the older rates: In case of TAXINN tax procedure, change the posting date to previous date for the old rates to be determined. In case of TAXINJ tax procedure, there are two options: 1. Change the rate percentage to new rate after foreclosing all open PO & GRs. 2. Create a new tax code with the new rates.

vii) For Customers who will be under the Service tax regime as part of Budget 2010: Ans: For Customers who will be under the Service tax regime as part of Budget 2010 and if the Standard Service Tax solution provided by SAP is not implemented yet, refer the following Notes for Customizing and service tax related solutions. NOTE 779512 and 778976 - Creating new Service Tax conditions for TAXINJ - MM and SD NOTE 921634 - Creating new Service Tax conditions for TAXINN - SD In case of TAXINN - MM module, please refer the attachment 'TAXINNMM.zip' for the steps to create the Service tax conditions NOTE 921634 - Please implement the note for Deferred Service Tax solution along with all the relevant Service tax notes.

III. Budget Announcements and impact on Logistics processes in SAP: Customers seeking support from SAP for Budget 2010 - 2011 must ensure they have carried out the Preparatory activity given in this note. Customers raising OSS messages for Budget 2010 must maintain the short text of the message as 'Budget 2010 - <>'.

#Incident:19 The changes that are made with this interface note are the prerequisite for implementing other SAP Notes. Note the following: This SAP Note does not contain the complete functional scope for the handling of blocked business partner data in MM Purchasing. This functionality is delivered only with a Support Package (ERP 617, Support Package 8). Reason and Prerequisites This interface note is a preparation note that does not interrupt operation. If this SAP Note is a prerequisite for subsequent corrections, implement it. Solution Implement this interface note only if it is required as a prerequisite for other SAP Note

#Incident:20 This note contains some corrections for Account Assignment in Create Purchase Requisition application Reason and Prerequisites Program Error Solution Implement the attached correction instructions or upgrade to the latest support pack

#Incident:21 1. Problems in computing Status in Purchase requisition app. 2. Purchase Requisition with Punch out Catalog Item are missing Account Assignment details. Reason and Prerequisites Program Error Solution Please implement attached correction instructions with this note

#Incident:22 This note updates release 6.18 with all changes done till note 2201883 included. Reason and Prerequisites Release 6.18 where enabled for the FIORI APP "Approve Purchase Requisition" in an older version. For to get the most recent status, we add all changes done in several notes in the meanwhile by this single note. Solution Enter the correction instructions into your system.

#Incident:23 Incorrect tax calculation or runtime error are observed while excise invoice capture at the receiving depot in J1IG transaction, when subtotal 4 and 6 are used in your MM pricing. Subtotal 4 and 6 of MM pricing procedure are used to manipulate tax base being passed for tax calculation. Standard routines 362 and 363 are used to handle these calculations. But when you use these subtotals to address your specific business requirement, Tax calculation at receiving depot happens incorrectly. Reason and Prerequisites A check is missing. SAP Notes 2304282 and 2313971 are prerequisites. Solution Implement the attached correction instructions. Reason and Prerequisites Reason: Correction to legal funtions. Solution 1. Carry out the manual steps as given in attached 'Manual_changes.docx'. 2. Implement the code corrections relevant for your release. Note 

Mark SUPRESS_4 as 'X' in Userexit 'J_1I7_USEREXIT_DEPOT_SELFLAG', if you are using subtotal 4 in your MM Pricing procedure.



Mark SUPRESS_6 as 'X' in Userexit 'J_1I7_USEREXIT_DEPOT_SELFLAG', if you are using subtotal 6 in your MM Pricing procedure.

#Incident:24 1) You transfer data from Materials Management (MM) or Sales and Distribution (SD) to Profit Center Accounting (PCA). The "Reference Fiscal Year" field remains blank. 2.) You use 1KE8, 1KE9, 1KEC, and 1KEA to post documents to Profit Center Accounting. When you do this, the documents are not reversed. Instead, they are posted twice. 3.) You can no longer use references to display profit center documents. 4.) Cash journal documents have an incorrect (non-initial) reference fiscal year.

Reason and Prerequisites You have implemented SAP Notes 1675896 and 2120836. These do not take into account the fact that the reference information from MM and SD is saved differently than the other applications. Program error Solution Implement the attached corrections or import the relevant Support Package into your system.

#Incident:25 Net value is greater than the target value for contracts Reason and Prerequisites Net value is greater than the target value for Contacts because of note : 1945876 Solution Please implement the attached correction instruction.

#Incident:26 On the ECC it is possible to customize the system in a way that it is not allowed to create negative stock in a plant. This can be done on the following levels:  



Material level (Material Master Record --> view General Plant Data / Storage 2 --> General plant parameters: Flag for "Negative stocks in plant") Storage location level (SPRO --> SAP Reference IMG --> Materials Management --> Inventory Management and Physical Inventory --> Goods Issue / Transfer Postings --> Allow Negative Stocks) Valuation area level (SPRO --> SAP Reference IMG --> Materials Management --> Inventory Management and Physical Inventory --> Goods Issue / Transfer Postings --> Allow Negative Stocks)

Negative Stock is allowed if the checkboxes are active. For unrestricted stock and blocked stock all three checkboxes need to be active to allow negative stock. For special stock it is sufficient to activate the storage location level and valuation area level checkboxes only. MDS always shows only a warning when negative stock is created and leaves the ERP customizing unnoticed.

Reason and Prerequisites At the moment MDS does not know the customizing for negative stocks on the mobile client and always allows to create negative stock with a warning message. The backend will execute the checks against the customizing and will return an error if negative stocks are not allowed. This forces the user to do an additional error handling on the mobile client. Solution Implement the following SAP Notes in your back-end system to enable the similar behavior and hinder the creation of negative stock on MDS if not allowed in the customizing. SAP Note 2251795 - MDS goods issue creating negative quantity - MMMATERIAL SAP Note 2249685 - MDS goods issue creating negative quantity - HRSTLOC SAP Note 2251796 - MDS goods issue creating negative quantity - CAT001W Create the following parameter in the customizing (SPRO --> SAP Reference IMG --> Defense Forces & Public Security --> Mobile Applications --> General Settings --> Specify Parameter Values):

COM.SAP.EA.DFPS.MM.CHECK_FOR_NEGATIVE_QUANTITY = X (Enable error message on MDS if negative quantity is not allowed)