SAP MM Support Issues

1. Value of Stock (BSX) in Goods Receipt for Purchase Orders with negative stocks

Issue:

You do not understand the value posted to the Stock Account (BSX) in a Goods Receipt for a
Purchase Order when the stock was negative before the posting.
Solution:
First consider the concept of negative stocks:
Negative stocks are allowed when the goods issue needs to be done urgently. Just due
to organizational reasons goods issues are entered before than the corresponding goods receipts.
Once the goods receipts have been posted, the book inventory balance must again correspond to
the physical stock, that is, the book inventory balance may no longer be negative.
Negative stocks are always a sign that physical movements must be entered in the system at a later
stage.
So that negative stocks are allowed, the 'Negative stocks' indicator should be marked into the
material master data via MM01/MM02 transactions on General Plant Data 2 view at ‘General Plant
Parameters’ screen.
• Customizing settings:

You have also to allow negative stocks by plant. You should customize your system to accept this
possibility. Go to SPRO->IMG->MM->Inventory Management & Physical Inventory->Goods
Issue/Transfer Postings->Allow Negative Stocks (OMJ1).
• System Messages:

Message ‘M7 021’ should be set as warning in OMCQ transaction.

In some cases, you can face the error message ‘M7 021’. It is not mandatorily related to stock
inconsistencies. It is hard-coded in several programs. See SAP note 24312 for more details. Example:
you have set this message as ‘w’ in OMCQ and set the negative stocks indicator into the material
master but you did not allow negative stocks in your customizing settings. In this case, error message
‘M7 021’ will be presented when doing the goods issue.
Example: Goods Receipt Valuation when allowing negative stocks
A) Notice you have negative stocks in MMBE transaction and a corresponding negative value in
MM03.
For example: -5 KG valuated at -350 EUR (Moving Average Price of 70 EUR/KG).
B) Create a Purchase Order in ME23N transaction for 10 KG.
C) Post a Goods Receipt for the Purchase Order in MIGO transaction for 10 KG.
D) Check stock position after posting the GR in MMBE transaction.
Goods receipt was done by 10 KG. So, we will have -5 KG + 10 KG = 5 KG.
E) Calculate the GR value (WRX).
Data (for example):
PO qty = 10 KG
PO Net price: 75 EUR
PO price unit: 1 KG
GR qty: 10 KG
Formulas:
PO Net Value = PO qty x (PO Net price / PO price unit)
GR value = GR qty x (PO net value / PO qty)
Calculation:
PO Net Value = PO qty x (PO Net price / PO price unit)
PO Net Value = 10 KG x (75 EUR / 1 KG) = 750 EUR.
GR value = GR qty x (PO net value / PO qty)
GR value = 10 KG x (750 EUR / 10 KG) = 750 EUR.
F) Calculate the stock account value.
Data (for example):
-5 KG valuated at -350 EUR (Moving Average Price of 70 EUR/KG).

Process:
The first 5 KG in the reception will clear the negative stock. After receiving the first 5 KG, the stock
will be zero. Since the stock will be zero, the value needs to be cleared also. The first 5 KG are
valuated at 350 EUR to clear the stock value.
Then, the remaining 5 KG are valuated according to the value given externally by the purchase
order:
5 KG x 750 EUR / 10 KG = 375 EUR.
The total value posted to stock is:
BSX = 350 EUR + 375 EUR = 725 EUR.

G) Calculate the price difference value.

PRD = WRX - BSX
PRD = 750 EUR - 725 EUR = 25 EUR.
H) Check FI document via ME23N (PO history), MB03 (via material document) or in FB03
directly. Considering the above example, you would see that stock account would be debited
on 725 EUR, clearing account would be credited on 750 EUR and, therefore, price difference account
would be debited on 25 EUR.

2. MB5T shows negative stock in transit

Issue:
The transaction MB5T shows negative Stock in Transit for a Cross Company Stock Transport
Order (Inter Company).

Solution:
 In Intra-Company Stock Transport Orders there is "real" stock in transit: When the goods issue is
posted from the supplying plant the system updates the stock in transit in the receiving plant
(MARC-TRAME).

In Cross-Company Stock Transport Orders there is not "real" stock in transit: When the goods
issue is posted from the supplying plant there is not any stock update in the receiving plant. The
goods issue in the supplying plant is totally independent of the goods receipt in the receiving
plant.

In this case the stock in transit is only "virtual": it is dynamically calculated by the program via
the purchase order history, as the difference between the goods receipt and the goods issue
quantity. Since we do not have any real stock in transit updated in any table, it can indeed be
negative, when, for example, the goods receipt is posted before than the goods issue

3. Error:
Error IO231 during goods movement
Reason:
This is usually caused by mismatch between serial number stock data and stock data in material
document posting. The detailed difference can be found
in long text display of error IO231. For example, if the serial number is already in stock, you can no
longer use it to post goods receipt.

Solution:
1. check the serial number data in transaction IQ03 and identify if the serial number has
corrected stock information
 For serial number 43, the stock in in return, so this serial number cannot be used for a goods
movement posted to unrestricted stock(stock type: blank).
2. If the stock information in serial number is consistent, then please change and select another
serial number which is suitable for the process to be
carried out.

3. If the stock information in serial number is inconsistentyou can execute physical inventory
using transaction MI10 to correct it into the correct status and
then continue with the business process.

4. Error: Error ME664 'Change Acct Assignment Cat. could not be effected' in service documents

Issue:
You want to change the account assignment category in service documents (EBAN-KNTTP, EKPO-
KNTTP) but the field is grey or (using BAPI) you receive information message ME 664 "Change
Acct Assignment Cat. could not be effected". The current account assignment category is not U
(Unknown).

Solution:
 As per standard system design it is not possible to change the account assignment category for
service items with account assignment category other than 'U'.
It was designed like that because the accounting is made at SERVICE level and not at ITEM level,
as for materials. For one item there can be several services with different account assignments.
Therefore, a change of the account assignment category at item level is not possible.
"It is now possible to change the account assignment category from 'Unknown' to something
else. Not however from (for example) 'cost center' to something else. This restriction only
applies to service and limit items. The field selection must also be set as a prerequisite as
described in note 313120 ."

5. Please change the Company or Plant or Storage location address

6. Create LSMW template for changing the Purchase group/Plant specific material status/ MRP
Type/MRP group etc.
7. Please guide me to cancel a material document in SAP?
Sol: Cancel the document by using MIGO-Cancellation
8. PR quantity is 50. PO is created with 40 quantity and GR, IR are also completed. We don’t
want to create further POs with this PR. Please suggest fulfilling this requirement.
Sol: Pre-close the Purchase requisition
9. Please provide the list of users who have access to ME51N transaction code

Sol: SUIM T code. Follow below path to go to next screen

After you click on By Transaction Authorizations, you will get below screen
 Execute to get the below list of users

10. Please delete the Purchase group Z01.

Sol: It is always suggested to change the description of the purchase group to DO NOT USE or
ABOSOLETE etc. but deleting a purchase group is not suggestible because that purchase group
would be used in many Purchase orders and release strategies etc. so reporting wise we may
face issues in future. If we change the description, the user will see the description before
he/she uses. As it is a configuration change, it should be handled through Change Request
process.

Path: SPRO T codeà IMGà Materials ManagementàPurchasingàCreate Purchasing Groups

11. Add new reason code to the movement type 322.
Sol: New reason code for any movement type can be added in the below configuration. As it is a
configuration change, it should be handled through Change Request process.

Path: SPRO T codeà IMGà Materials Managementà Inventory Management and Physical
Inventoryà Movement Typesà Record Reason for Goods Movements

Once you click on Reason for Movement. Below screen will be appeared. Click on New entries
and give the respective details.
12. Please provide the list of approvers who approved a PO xxxxxx
Sol: You can get the list of approvers from the Header changes of the PO and you can get the
user ids through the roles of the respective Release codes of the PO at that point of time.
13. Please activate the release procedures to the Purchase orders with Account Assignment
Category ‘K’.
Sol: Go to CL20N and add ‘K’ to all the release strategies under characteristics Account
Assignment category.

Below is the initial screen of CL20N. Give Purchase group, Release strategy and Class type as
inputs.
14. Change the PR approver for the combination of Release group V1 and Release strategy 01
from Ganesh to Suresh.
Sol: Above requirement will be fulfilled with below steps
A. Go to the table T16FS and give respective release group and release strategy as input and
execute
Get the Release code as output

B. As per the customization of your company role setup, identify the role against the release
code.
It will be generally PREL+ Release group _Release code i.e. PRELV1_10
C. Go to the T code PFCG and give the respective role as input to see the User who is assigned
to the role under User tab. In this case, it is GANESH.

Request Authorization team to remove the user GANESH and add SURESH to the role
PRELV1_10

And also above requirement will be fulfilled by changing the Release codes in the
prerequisites of the release strategy if GANESH and SURESH belong to different release
codes. For example, GANESH code is 10 and SURESH code is 11.
 Path: SPRO T codeà IMGà Materials ManagementàPurchasingà Purchase Requisitionà
Release Procedureà with Classificationà Set Up Procedure with Classificationà Release
strategies

15. Specific fields must be changed for a released Purchase Requisition.

Solution: This functionality is available for only Purchase Requisition. We can activate required fields
to be changed for a released Purchase Requisition with below configuration settings. Required field
selection key has to be assigned to the Released indicator.

Path: SPRO T codeà IMGà Materials ManagementàPurchasingà Purchase Requisitionà

Release ProcedureàProcedure with Classificationà Set Up Procedure with Classificationà
Release Indicator
16. Purchase Requisition should not be changed with ME52N after PR is released.

Solution: Keep the changeable option as ‘1’ for the Released indicator. Settings can be done at
below Path

Path: SPRO T codeà IMGà Materials ManagementàPurchasingà Purchase Requisitionà

Release ProcedureàProcedure with Classificationà Set Up Procedure with Classificationà
Release Indicator
17. The field of 'Total value' in PR creation screen was disappeared

Solution: Open the PR creation screen with ME51N and check the layout which was selected and
check whether Total Value is added in display columns or not
After clicking on change layout, you will get below screen. Check total value is in displayed columns
or not.

18. Create stock in Test system for a material.

Solution: Getting stock for any testing purpose can be done from any of below processes.

• Initial entry of stock with movement type 561

• Goods Receipt without Purchase Order – 501 Movement Type
• Goods Receipt with Purchase Order – 101 Movement type

19. Excise duty is not populating at the time of PO creation?

Solution: This kind of error will come when there is change in excise rate date was changed for
Chapter ID. So we need to give J1ID excise rate effective dates from PO raised date

20. Error:
Solution:
When we get this error, we should first check the assignment of Financial year variant with the
Company Code. T Code is OB37
Maintain the financial year variant and assign to Controlling area in OKKP

If the issue is still there, you check whether the Posting Period variant is there or not.
You can assign the same in transaction code OBY6 also
 21. The change log of the purchase order shows the transaction ME23N. Change log of PO is
showing ME23N which should be shown ME22N. What is the reason?

Sol: Item Changes will be saved in ME23N, if this transaction was used to enter PO. Item Changes will
be saved in ME22N only if you go directly to this transaction to perform the changes.
There are following notes, which explain the ENJOY-functionality: 491789 and 212447
In the header modules, you obtain the SAP transaction category via the parameter I_TRTYP:
-> A Display
-> V Change
-> H Create
The same is valid for ME52N and ME53N (Purchase Requisitions).

22. User wants to perform Invoice verification before GR in Service Procurement

Sol: Invoice Verification for Services procurement happens based on Goods Receipt I.e. Service Entry
sheet which generates GR document automatically in the backend.

This is only possible if you use Public Sector and Funds Management (PSM-FM).

1. Activate the Enterprise Extensions Public Sector, for this go to:

SPRO -> Activate SAP ECC Extensions -> Here activate EA-PS.
2. You must have set the Invoice Before Goods Receipt Allowed indicator in the Follow-On
Processing for External Service Items area of Customizing for Materials Management under:
External Services Management -> Source Determination and Default Values -> Define for the
Client (transaction ML91)

If you activate the above settings, then system should not give the error message when you
unselect GR indicator in a service PO.

23. Valuation for Reversals and Return deliveries for Goods Receipts for Purchase Orders

Issue:

You do not understand the value posted to the GR/IR Clearing Account (WRX line in the Accounting
Document) in a return movement (122) or in a cancellation (102).

Solution:

The valuation of reversals (movement type 102) and return deliveries (movement type 122) is based
on the previous postings in the PO History.

For the valuation of the reversals the system compares the quantity received so far against the
quantity invoiced so far.

1) When the invoiced quantity is higher or equals the received quantity, the reversal is valuated
according to the invoiced value:

Reversal = Quantity in the cancellation x (Invoiced value / Invoiced quantity).

2) Otherwise, the valuation is based on the clearing value:

Reversal = Quantity in the cancellation x (Clearing Value of the Invoices - Goods Receipt Value) /
(Invoiced Quantity - Goods Receipt Quantity).
Note: The Clearing Value of the Invoices might be different from the Invoiced Value. The Clearing
Value of an Invoice is the amount posted the GR/IR Clearing Account in the corresponding
accounting document (WRX posting key). It can be seen in the Purchase Order history switching to
the Clearing Value view or directly in the table EKBE (field AREWR for the local currency and field
AREWB for the PO currency).

If no invoices have been posted, this formula is reduced to:

Reversal = Quantity in the cancellation x (Goods Receipt Value) / (Goods Receipt Quantity).

So, the reversal is valuated according to the average values received as explained in the note 49995
Case A.

24. The period concept - Clearing the stock

Issue:
You need to clear the stock of a Material in a Plant and a Storage location because you want to,
for example, change an important indicator in the material master (like the Batch Management
Indicator).

This requires that the stock is zero in both, the current and the previous period.

Solution:
The stock of a material is managed monthly in the stock and valuation tables.

You need to consider that a posting in the previous period (i.e. with a posting date in the
previous period) will always affect your stocks in the current period.

If you need to clear the stock in the two periods you will need to consider what is the situation
before the posting in both periods:

Case 1) Same quantity in the two periods:

Previous period: 10 PC.

Current period: 10 PC.

A goods issue of 10 PC in the previous period (with a posting date in the previous period) will
clear the stock in both periods.

After the posting of the goods issue you will have:

Previous period: 0 PC.

Current period: 0 PC.

Case 2) More quantity in the current period:

Previous period: 10 PC.

Current period: 15 PC.

A goods issue of 15 PC in the previous period (with a posting date in the previous period) will
not be possible because there is not stock enough in the current period to carry out the posting.

The system will send the error message M7021 with the short text "Deficit of SL Unrestr. prev. 5
PC" where the term "prev" indicates the previous period.

To clear the stock in this case the posting should be made as follows:

A goods issue of 10 PC in the previous period will clear the stock in the previous period and will
leave 5 PC in the current one.

After the posting of the goods issue you will have:

Previous period: 0 PC.

Current period: 5 PC.

You will then need to post a further goods issue of 5 PC in the current period to clear the stock
completely.

Case 3) More quantity in the previous period:

Previous period: 10 PC.

Current period: 5 PC.

A goods issue of 10 PC in the previous period (with a posting date in the previous period) will
not be possible because there is not stock enough in the current period to carry out the posting.

The system will send the error M7021 reporting a deficit of 5 PC in the stock of the current
period.

The posting should be made as follows:

 You need to post a goods receipt of 5 PC in the current period.
After the posting of the goods receipt you will have:
Previous period: 10 PC.
Current period: 10 PC.
A goods issue of 10 PC in the previous period will now be possible and you will be as in the Case
1)
25. ME52N Field is not editable
Issue:
ME52N field is not editable.
Solution:
The field is set as "Display" in relevant "Field Selection Key" in customizing (T-code OLME >
Purchase Requisition > Define Screen Layout at Document Level). Please refer to SAP Note
30316for more detailed information.
Field "Purchase order price" (EBAN-BPUEB) is set in the Purchase Requisition (PR). (Can be
checked via T-code SE16)

26. Default field selection settings on ME53N

Issue:

Relevant fields should not be displayed according to default settings ("Choose layout... > change
layout...") in T-code ME53N.

Steps:

Set a field (For example, "Release Date") as no display column via "Choose layout... > change
layout..." in T-code ME53N.

Run T-code ME51N to create two Purchase Requisitions (PRs -For example, PR1 and PR2).

Run T-code ME53N to display PR 1, and find the field (For example, "Release Date") does not
display.

Click "Other Purchase Requisition" button and enter the number of PR 2.

Click "Other Purchase Requisition" button and enter the number of PR 1.

The field (For example, "Release Date") displays.

Solution:

The default setting (in T-code ME53N) is considered by system only for the first run of T-code
ME53N.

Please consider setting the field as "optional" or "hidden" in customizing (T-code OLME >
Purchase Requisition > Define Screen Layout at Document Level).
27. Closed purchase requisitions and MRP

Issue:

You want to understand which PR is considered by MRP as closed.

Solution:

A requisition is considered closed for MRP and other when:

The closed indicator is set.

The deletion indicator is set.

The requisition quantity is less than or equal to the corresponding PO item.

The 'closed' indicator on a purchase requisition can only be set manually. This can be done with
one of the following methods:

In the change requisition transaction ME52/ME52N, set the close indicator

In ME57, while creating a PO with reference to a requisition, set the close indicator on the item
selection screen

After converting PR to a PO, if PO quantity is reduced, system will use the same PR to meet the
quantity that is not enough,

PO will have the delivery schedule. In the delivery schedule it is possible to see that system is
referencing the PR and the item. Hence, system keeps PR details.

When another delivery schedule quantity is added into the PO with reference to the PR item,
system will further adjust the open PR.

This would not create an excess stock situation, since MRP created the PR to meet the
requisition and PO is for less quantity than required.

28. Source of supply not taken in Purchase Requisition

Issue:

The purpose of this page is to show how a source can be determined correctly in purchase
requisition.

Solution:
 The system automatically locates the correct info record/vendor through source determination
when Flag 'Source Determination' is checked in ME52N/ME51N and Purchasing organization is
not manually entered in the PR item line

As soon as the purchasing organization information is entered manually in the requisition line
item, source determination is not run, and the info record is not determined which leads to the
source not been determined in the purchase requisition. This occurs because the purchasing
organization field is part of the MM internal source of supply record. When this field is entered
in the PR line item, it also becomes part of the source of supply tab for the item and the system
then assumes that the user wishes to manually assign the

source of supply based on the purchasing organization. Therefore, the vendor for the item can
only be filled by entering it manually or through the 'Assign source of supply' button in the
Source of Supply tab.

29. Error ME083 'Enter cost center' in ME51N

Issue:
ME 083 - 'Enter cost center' in ME51N
Solution:
Check if indicator 'Agreement' is set in customizing:
SPRO > Financial Accounting > Asset Accounting > Integration with the General Ledger >
Additional Account Assignment Objects > Activate Account Assignment Objects
In the Menu bar: EDIT > Change field content. Turn off indicator for 'Agreement' for KOSTL

30. Default document type in ME51N

Issue:
You would like to understand the logic for the default document type in ME51N.
Solution:
System takes default document type for Purchase Requisition (PR) according to following
priority:
Settings “Personal Setting" in T-code ME51N.
"Default Purchasing Document Type in Transactions" for T-code ME51N in customizing table
T160 (T-code OLME -> Define Default Values for Document Type).
User parameter "BBA" in T-code SU01 or SU3.
The first available document type in customizing table T161 (T-code OLME -> Purchase
Requisition -> Define Document Types)
31. While creating PO we enter tax code in invoice tab in item detail to see the flow of taxes, though
condition record were maintained through FV11, with reference to same tax code and condition
type which was used in PO.

ISSUE- Tax was not flowing in PO

Solution- validation date need to change in condition record in FV11 based on which tax code and
condition type is used, then it will replicate in PO with taxes.

32. PO's has been created and they were wrongly inputted the wrong cost center and did all the
GR's and IR's against them.

ISSUE- As per accounting entries triggered wrong G/L account

Solution- First the IR's were reversed through MR8M, then GR's were reversed through MIGO,
Cancellation against Material documents, then PO was unreleased, then in ME22n, the cost center
numbers were changed, then all the GR's and IR's were done again for those PO's.

33. Import PO was created with freight condition also with separate vendor, then we do custom
MIRO, were goods supplier and planned delivery cost were selected, but as per requirement
freight separate payment was required.

ISSUE- custom payment and freight payment came same time to single vendor

Solution- First only planned delivery cost must be selected in MIRO for custom duty payment and
then post it then for freight separate payment must be done as per freight vendor after GR.

34. Service PO was created with all inputs and data after giving tax code in invoice tab, taxes were
unable to display.

ISSUE- taxes were not able to display

Solution- even though we enter tax code in invoice tab then also we need to enter tax code in
service line item, then tax can be displayed.

35. In subcontracting process, when we create PO, then transfer posting, then we create challan,
while creating challan.

ISSUE- Pricing error comes

Solution- maintain the pricing condition type in V/08 subcontracting pricing procedure, and maintain
that condition type in OVKK with reference to document pricing procedure which also must be
maintained in VOFA, then this issue can be resolved.

36. User posted MIRO. Due to some reason he wants to cancel that invoice.
 But while cancellation system is showing error like "balancing filed for the profit centre is empty
for the item 4".
Solution; with help of fico consultant they maintained cost element for that item (GL AC)
After that they maintained cost center in that profit center.

37. making HSN code mandatory in PO and MIRO screen

Solution is through SHD0 transaction I did mandatory
38. Client asked 2 new tax codes (5%and18%) for import IGST RCM
Solution is created 2 new condition types
Assigned in pricing procedure and did required configuration

39. Please change the Company or Plant or Storage location address

40. Create LSMW template for changing the Purchase group/Plant specific material status/ MRPT
type/MRP group etc.
41. Please guide me to cancel a material document in SAP?
Sol: Cancel the document by using MIGO-Cancellation
42. PR quantity is 50. PO is created with 40 quantity and GR, IR are also completed. We don’t want
to create further POs with this PR. Please suggest fulfilling this requirement.
Sol: Pre close the Purchase requisition
43. Please provide the list of users who have access to ME51N transaction code

Sol: SUIM T code. Follow below path to go to next screen

After you click on By Transaction Authorizations, you will get below screen
 Execute to get the below list of users

44. Po workflow showing erroneous status?

Sol: Logically delete the workflow T Code-SWIA

45. When displaying Purchase Requisition (PR) by T-code ME53N, the screen layout of field is
different if there is release strategy
Sol:

Reproducing the Issue

1. Run T-code ME51N to create two PRs. (for example, PR 1 without release strategy and PR 2 with
release strategy)
2. Run T-code ME53N to display PR 1 and PR 2.
3. The screen layout of a field (for example, material) is different (for example, 'display' in PR 1, but
'hidden' in PR 2).

Cause

The settings for "Field Selection Key" of relevant Release ID is also considered by system if there is
release strategy in PR.

Resolution

1. Run T-code ME53N to display PR 2.

2. Check the Release Indicator for this PR (for example, B).
3. Check what is the "Field Selection Key" for Release Indicator B in customizing (T-code OLME ->
Purchase Requisition -> Release Procedure -> Procedure with Classification -> Set Up Procedure
with Classification -> Release Strategies).
4. Adjust the screen layout settings of the "Field Selection Key" which found in STEP 3 in
customizing (T-code OLME -> Purchase Requisition -> Define Screen Layout at Document Level)
 46. "Down Payment percentage" and "Due date" are specified at Purchase Order (PO) header level.
These percentages and due dates are not adopted automatically to all PO items.
Business function LOG_MMFI_P2P has been activated

Cause

If down payment data is defined on PO header level it means that it cannot be assigned during PO
creation to a specific PO item.

SAP does not provide an algorithm that automatically drills down from the header Down Payment data
to all items of a PO.

This requires a manual input.

Resolution

There are 2 options:

1. Define the down payment data only at item level (not at header level) in order to reduce manual
entry.
2. Make use of BADI ME_PROCESS_PO_CUST to copy the values from header into all items

47.
You flag a purchasing info record for deletion. When you create purchasing documents
(purchase order, outline agreements, RFQ), the values from the deleted info record are
adopted.

Cause

System design.

Resolution

This behavior is not an error, but the intended system design. The data in the info record that is marked
for deletion is still considered valid. If you do not wish that this data is adopted into purchasing
documents, you need to archive the info record. Alternatively, you can set the system message 06 718
to error via transaction OLME -> Environment Data-> Define Attributes of System Messages.

There is also the below modification proposal- If you apply this modification, deleted info record
data will no longer be proposed:

Function module: ME_EINA_SINGL_READ_MATNR_LIFNR

 IF SY-SUBRC <> 0.
SELECT SINGLE * FROM EINA INTO PO_EINA
WHERE MATNR = PI_MATNR
*>>>> START OF DELETION <<<<<
AND LIFNR = PI_LIFNR.
* and loekz = ' '.
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
AND LIFNR = PI_LIFNR
AND LOEKZ = ' '.
*>>>> END OF INSERTION <<<<<<

48. No labels are printed when a goods movement is posted using the transaction MIGO. The
number of GR slips is 000.

Sol:

For all movement types (e.g. 101), for which label printing is desired, you must maintain
movement-type-dependent field selection.

You will find this Customizing under:

Materials Management --> Inventory Management and Physical Inventory --> Settings for Enjoy
Transactions --> Settings for Goods Movements (MIGO) --> Field Selection per Movement Type.
Include the field WEANZ as an optional or mandatory entry field for the desired movement types.

49. You want to release a service entry sheet for an MAA service purchase order item with planned
delivery costs. Why does error M7 599 "Inform system administrator: error at data
inconsistency multiple account assignment" prevent this release posting?

Sol:

planned delivery costs are generally not supported in External Services Management and for blanket
purchase orders, item category D or B.
In the business function "LOG_MM_MAA_1", it is possible to process service purchase order items with
multiple account assignment and valuated goods receipts only without planned delivery costs. The
design of this business function does not allow planned delivery costs for MAA service purchase order
items.

When posting the goods receipt for MAA purchase order items, the system checks the data to be posted
for consistency. If this data is not consistent, the posting of the goods receipt terminates with error
message M7 599. This message should prevent data inconsistencies.

50. In a scheduling agreement Delivery Completed Indicator (ELIKZ) is not set automatically when
doing a good receipt. Why?

Sol:

For scheduling agreements, you must maintain the final delivery indicator only in the scheduling
agreement item.

A maintenance from the goods receipt is useless for scheduling agreements since the current schedule
line situation is generally not final. Even if all schedule lines are supplied, this does not mean that no
new schedule line might be added. Therefore, for scheduling agreements, maintenance of final delivery
indicator is planned only from the document item.

Many Support issues will be related to existing custom reports or forms or

enhancements. So, these can’t be provided like above but I give few
examples below

• Addition of remarks or new fields in existing smart forms like PO or GR

Note or Reservation Slip
• Value is wrong when the price is crossing 6 digits- Need to check with
ABAP and fix the length issues
• Custom Reports – Addition of new fields or getting wrong values in
reports etc.
• In one custom report, all the PO items are getting same Net price.
• Reason would be wrong coding. ABAPer would be missed to add PO
item in loop when he gets the Net price. So, program is showing the
net price of first Line item for all the items.