High volume of IDocs currently stuck in 'Pending' status

 Issue: Slow performance in delivery update batch job. 

Context: 1000 deliveries processed for pick/pack and PGI.

Impact: High volume of IDocs currently stuck in 'Pending' status.

 

Solution:
To address the slow processing of delivery updates and the backlog of IDocs for 1000 deliveries, we can look into several performance optimization strategies in SAP.

1. Enable Parallel Processing for IDocs (Recommended)

If your IDocs are stuck in status 64 (ready for transfer to application), the background job (transaction RBDAPP01) can be configured for parallel processing.

• How to do it: When scheduling the background job for RBDAPP01, check the "Parallel Processing" flag in the selection screen.
• Server Group: You will need to specify a server group (defined in transaction RZ12) to distribute the load across multiple application servers.
• Packet Size: Adjust the "Packet Size" (usually 20-50). Smaller packets allow for better distribution but more overhead; larger packets reduce overhead but can cause "bottlenecks" on a single process.

2. Optimize Collective Processing for Deliveries (VL06G / VL10CU)

If the bottleneck is the actual PGI/Delivery update (and not just the IDoc layer), you should verify the configuration for collective processing.

• Parallel Processing Profile: Go to transaction VL10CU (or via SPRO: Logistics Execution > Shipping > Deliveries > System Modifications > Specify Parallel Processing).
• Application: Create or update a profile for application V5 (Shipping). Here, you can define how many parallel processes the system is allowed to spawn during collective PGI.

3. IDoc "Inbound" Processing Mode

Check how your partner profile is set up in transaction WE20.

• Processing Selection: Ensure that the "Inbound Options" are set to "Trigger by background program" rather than "Trigger immediately."
• Why: "Trigger immediately" forces the system to process IDocs one by one as they arrive, which can lock the delivery table (LIKP/LIPS) and cause sequential wait times. Using a background job allows you to control the timing and use the parallel processing mentioned in Step 1.

4. Check for Database Locks (SM12)

With 1000 deliveries being updated simultaneously, you are likely to have significant contention for the LIKP (Delivery Header) and VBFA (Document Flow) tables.

• The Issue: If your IDocs are trying to update the same document or related documents (e.g., shipments), they will wait for each other.
• Resolution: Check transaction SM12 to see if there are many entries for table LIKP. If one large job is locking many deliveries, parallelizing the IDoc processing into smaller, distinct "packets" of delivery numbers will help reduce lock contention.

5. Review System Resources (SM50 / ST03N)

• SM50: Check if your background work processes (Type: BGD) or Update processes (Type: UPD) are all "Private" or "Full." If they are, parallel processing won't help because there are no available slots.
• ST03N: Look at the "Roll-in" and "Wait" times for your background jobs. High wait times indicate that the system is CPU-bound or I/O-bound.

Summary of Next Steps:

1. Stop the current single-threaded job if it is barely moving.
2. Split the IDocs into smaller batches.
3. Restart the processing using RBDAPP01 with the Parallel Processing flag enabled and a valid RZ12 Server Group.

ASN (Advanced Shipping Notification) errors in SAP

 

Solving ASN (Advanced Shipping Notification) errors in SAP typically involves checking master data, inventory availability, and document links.

How to troubleshoot and solve each of the errors you listed:

1. No Component XXXXX found for BOM Material

Reason: This usually occurs for Subcontracting POs or Sales Sets. The ASN is trying to report a component that is not listed in the Bill of Materials (BOM) for that parent material.

• Solution:
• Check transaction CS03 (Display BOM) for the parent material and plant. Verify if component XXXXX is present.
• Check ME23N (Purchase Order). Go to the "Material Data" tab and click the Components icon. If the component is missing there, you may need to update the PO or the BOM and re-explode the components.
• Check the Validity Date of the BOM.

2. No inbound delivery created for Purchase Order XXXX

Reason: The system failed to generate the Inbound Delivery document despite receiving the ASN signal.

• Solution:
• Go to ME23N and check the "Confirmation" tab of the PO. Ensure the "Confirmation Control Key" is set to 0004 (Inbound Delivery) or similar.
• Check transaction SPRO for the confirmation control settings to ensure "Create Inbound Delivery" is enabled.
• Check VBG1 (Output determination) to see if there is an error in the output type used for the ASN (usually DESADV).
• Check SM37 or WE02 (IDoc monitor) to see the technical log of why the delivery creation failed.

3. Material SD status is incorrect for Material

Reason: The material has a "Sales and Distribution" status that blocks it from being processed (e.g., it is marked for deletion or set to "Blocked for Delivery").

• Solution:
• Go to MM02 (Material Master).
• Check the Sales: Sales Org. 1 view. Look at the field "X-distr.chain status" or "DChain-spec. status".
• If it is set to a status like 01 (Blocked), change it to a valid status or check with the Master Data team to see if the material is allowed to be shipped.

4. No data found for the Documents present in ASN

Reason: The ASN contains references to POs or items that the system cannot find, or the mapping between the incoming file and SAP fields is incorrect.

• Solution:
• Check transaction WE02 or WE05 to look at the incoming IDoc. Verify that the BELNR field (PO Number) and the POSNR field (Item Number) exactly match the PO in SAP.
• Ensure the Vendor in the ASN matches the Vendor in the Purchase Order.
• If you are using an EDI provider, ensure they are sending the correct PO number.

5. Item 000030: Only 0 ST from material XXX are available

Reason: This is a stock availability issue. You are trying to confirm a shipment for a quantity that the system believes is not in stock.

• Solution:
• Go to MMBE or MD04 to check the stock levels of the material in the specific plant and storage location.
• Check if the stock is "Unrestricted" or if it is tied up in "Quality Inspection" or "Reserved" for another order.
• If the material is a Batch managed material, ensure the specific batch mentioned in the ASN has enough stock.

 

General Troubleshooting Tool:

If these errors are appearing in an incoming IDoc, use transaction WE19 (IDoc Test Tool). We can copy the failed IDoc, fix the values (like the PO number or the Status), and re-process it to see if it clears the error.

 

S/4HANA: MCEX185 Error while reading table TMCEXUPD

 An issue preventing us from posting Goods Receipts against Purchase Orders and the error message we're seeing is "Error while reading table TMCEXUPD. 

We are  currently facing an issue preventing us from posting Goods Receipts (GR) against Purchase Orders, and the error message we're seeing is "Error while reading table TMCEXUPD."

This particular error (Message no. MCEX185) typically occurs because there are missing entries in either the TMCEXUPD or TMCEXACT tables within our current SAP client configuration. This is crucial for various SAP operations, including Goods Receipts.

To resolve this and allow for GR postings:

1. Verify Tables: We need to check the contents of tables TMCEXUPD and TMCEXACT in our current client.
2. Compare with Client 000: Compare these contents with the standard SAP "Client 000."
3. Copy Missing Entries:
• If entries are present in Client 000 but missing in our client, we should copy them overusing a standard SAP transport.
• If Client 000 also lacks the entries, we'll need to source them from another functional SAP system.

Important: Please ensure that only standard SAP client copy or transport tools are used for this process, as direct database manipulations are not effective for this specific issue.

Please contact your ABAP consultant to resolve this issue.

SAP Error: Special Stock E not supported (check your entry)

 

The SAP error "Special Stock O not supported (check your entry)" typically arises during a goods movement where you're trying to use a special stock indicator that's not allowed for that particular movement type or transaction.

Here's a breakdown of why this error occurs and how to troubleshoot it:

Special Stock Indicator "O": Special stock "O" typically represents "Customer Stock on Own Site" or "Make-to-Order Customer Stock". It signifies stock that is owned by the customer but physically located at your premises.

Movement Type Incompatibility: The most common cause of this error is using special stock indicator "O" with a movement type that doesn't support it. Certain movement types are designed for specific stock categories (unrestricted stock, quality inspection stock, blocked stock, etc.). If you're using a movement type intended for unrestricted stock with special stock "O," the system will throw this error.

Transaction Code Incompatibility: Similar to movement type incompatibility, the transaction you're using might not be designed to handle special stock "O".

Configuration Issues: There might be configuration issues within your SAP system related to special stock handling or the specific movement type you're using.

How to Troubleshoot:

Verify the Movement Type: Double-check the movement type you're using. Ensure it's the correct one for moving stock designated as "Customer Stock on Own Site". Consult your company's SAP documentation or your SAP Super User for the appropriate movement type for this scenario.

Check the Transaction Code: Make sure you're using the correct transaction code for the intended movement. Some transactions might not support special stock handling.

Review SAP Configuration (with appropriate authorization): If you have the necessary authorizations, you can check the configuration settings for the movement type and special stock handling in your SAP system. Transactions like OMJJ (for movement types) and related customizing transactions can provide insights. However, it's generally recommended to involve your SAP functional team or IT support for configuration changes.

Inspect Material Master Data: Review the material master data for the material you're trying to move. Ensure that the material is set up correctly for special stock handling.

Consult with your SAP Super User or Support Team: They are the best resource to help you identify the root cause of the error and determine the correct procedures or configurations for handling special stock "O" in your specific SAP environment.

This error highlights the importance of using the correct movement types and transaction codes when working with special stocks in SAP. Because the system needs to track inventory accurately, it enforces strict rules about which movements are allowed for each stock category.

SAP Error Message VL365 - Increment & & not complied with

 SAP Message VL365 is issued when changing quantity for batch split item in VL02N

Issue

• System is displaying message VL365 'Increment & & not complied with' in batch split screen even when just clicking enter in VL02N.
• Message VL365 is pop-up when changing batch split quantity.

Reproducing the Issue

1. go to VL02N, input delivery number.
2. select main item 10 and click 'batch split' button.
3. enter or changing quantity.

Root Cause

Ø  The "Delivery Unit" field is maintained in the material master data Sales View (MM03).

Ø  As per the F1 Help of field MVKE-SCMNG, as follows:

Delivery unit

Only exact multiples of this number can be delivered.

Example

Ø  The delivery unit consists of a number and a unit of measure. In the case of a delivery unit of 30 pieces,
30, 60, 90, and so on pieces can be delivered, but not, however, 100 pieces.

 

Ø  The system will check that the delivery quantity is in multiples of the delivery unit specified and raise VL365 if otherwise during the delivery process.

Solution

Ø  This message can be identified as either a warning or error message when customizing OVM1 transactions.

Ø  If the message is set as an error message, then, the delivery creation is prevented. During the creation of the delivery, the system issues message VL 365 to inform the user that the delivery unit condition has not been met, based on the MVKE-SCMNG setting in the material master.

Ø  If the message is set as a warning message, then, the delivery creation won't be prevented. System has just issued a warning in case such a requirement is not met during the delivery creation. However, for batch split scenario, system would pop-up this message in case the requirement is not met for main item.

Planned Post Goods Issue Date is the same as Delivery Date

 While creating a STO - Outbound delivery through VL10B, the Planned Delivery Date (Planned PGI date) is the same as the STO Delivery date in ME23N. 

For example, it takes 20 days to deliver to the receiving plant. It is expected that the picking/loading/goods issue should be proposed at least 20 days before the delivery date.

Issue

Create an Outbound Delivery by VL10B against a STO;

Check the Planed GI Date on Outbound, it is the same date as Delivery date on STO.

Reason

Missing configuration Settings.

Solution

Ø  Transaction code 0VLK and set "Rescheduling" as ‘X’ for delivery type involved on the flow(NLCC for example).

Example:

Blank   No rescheduling

X          Reschedule if deadlines are in the past

Y          Like X or route changed or route schedule changed

A          Reschedule after relevant changes

Transaction code OVLY, SD scheduling is not active, DlvSchelg and TranspSchd need to be ‘X’, for order type DL

SAP Error message VL607 given while doing PGI in VL02N

For plant &, material type & is not defined in Table T134W

Issue:

• While doing the PGI in VL02N, the system prompts error "For plant &, material type & is not defined in Table T134W". 

Root Cause

The current values in transaction OMS2 is causing the issue

Solution

1. Run transaction OMS2
2. Select the affected "Material Type" 
3. Double click on "Quantity / Value Updating" folder
4. Set flag "Qty Updating" and "Value Update" for the affected Plant / Material

Common Errors in SAP STO and How to Solve Them

 Here are some common errors encountered when working with Stock Transport Orders (STOs) in SAP, along with potential solutions:

1. Error: "Plant XXXX is not defined for stock transfers."

Cause: The sending or receiving plant might not be configured for stock transfers in the system.

Solution: Check the customization settings for both plants in IMG (Implementation Guide) under Materials Management -> Purchasing -> Purchase Order -> Set Up Stock Transport Order.

Ensure that the plants are assigned to the correct shipping points and receiving points.

2. Error: "No delivery type found for stock transport order type XXXX."

Cause: The delivery type assigned to the STO type might be incorrect or missing.

Solution: Verify the assignment of the delivery type in customizing under Logistics Execution -> Shipping -> Deliveries -> Define Shipping-Relevant Fields and Check Item Category.

Ensure the delivery type is relevant for STOs (e.g., NLCC for inter-company STOs).

3. Error: "Material XXXX does not exist in plant YYYY."

Cause: The material might not be extended to the sending or receiving plant.

Solution: Use transaction MM01 to extend the material master record to the relevant plants.

Ensure that the material is active and available for use in those plants.

4. Error: "No suitable storage location found for material XXXX in plant YYYY."

Cause: The system cannot determine a suitable storage location for the material in the receiving plant.

Solution: Define storage location determination rules in customizing (Logistics Execution -> Warehouse Management -> Master Data -> Storage Location).

Manually assign a storage location in the STO or during goods receipt.

5. Error: "Account determination for entry XXXX not possible."

Cause: The system cannot determine the appropriate GL accounts for the STO transaction.

Solution: Configure the necessary account determination settings in Financial Accounting -> Financial Accounting Global Settings -> Tax on Sales/Purchases -> Account Determination -> Account Determination Without a Country.

6. Error: "Delivery cannot be created for STO: Inconsistency in schedule lines."

Cause: There might be discrepancies between the STO schedule lines and the delivery creation settings.

Solution: Check the schedule line categories in the STO.

Ensure that the shipping point and route determination are set up correctly.

7. Error: "Stock of material XXXX in plant XXXX is insufficient for stock transfer."

Cause: The sending plant does not have enough stock of the requested material.

Solution: Verify the available stock in the sending plant.

Adjust the STO quantity if needed, or procure additional stock.

General Troubleshooting Tips:

Check the transaction logs (using transaction code SM13 or SLG1).

Use SAP Notes search (transaction code SNOTE) to find relevant SAP notes that address the specific error.

Consult with your company's SAP support team or a qualified SAP consultant for further assistance.

Determining the picking location automatically in SAP Delivery

Picking location determination for STO

Manually determining picking locations for every outbound delivery in SAP can be a tedious and error-prone process, especially in fast-paced warehouse environments. Fortunately, SAP offers various configurations and functionalities to automate this process, allowing for a more efficient and streamlined warehouse workflow.

This blog post will guide us through the key concepts and configuration steps to achieve automatic picking location determination in the SAP system.

Understanding the Fundamentals

Before diving into configurations, let's clarify some core SAP concepts related to picking location determination:

Ø  Picking Location: This is the physical location in the warehouse where the stock is stored and from where the picker retrieves the materials for an outbound delivery.

Ø  Shipping Point: This organizational unit represents the point from which outbound deliveries are shipped to the customer.

Ø  Plant: A plant in SAP represents a physical location where materials are manufactured, stored, or distributed.

Ø  Storage Location: A storage location is an organizational unit that subdivides a plant according to the purpose of the storage space (e.g., raw materials, finished goods).

Whenever we create the deliveries for STO, we will see that the storage location is missing for the items if the picking location is not determined automatically.

In order to perform picking and goods issue we need to enter the storage location manually for each item in the delivery.

To avoid the manual entry of storage location for each item in delivery we can configure the system to determine it automatically.

Configuration settings required:

Step1: Define the rules for picking location determination.

IMG-> Logistics execution-> Shipping-> Picking-> Determine picking location-> Define the rules for picking location determination.

In this step, you assign the rule to determine the storage location to delivery type.

Step2:  Define storage conditions:

IMG-> Logistics execution-> Shipping-> Picking-> Determine picking location-> Define storage conditions

In this step, you define the shipping conditions which are used in the rule to determine the storage location.

Step3:  Assign picking locations

IMG-> Logistics execution-> Shipping-> Picking-> Determine picking location-> Assign picking locations

In this step, you assign the storage location which should be populated in the delivery item for the rule conditions (combination of shipping point/plant/storage condition).

Step4:  Defining the automatic determination of storage location for delivery item category

IMG-> Logistics execution-> Shipping-> Deliveries-> Define item categories for deliveries

Master data setting:

We need to assign the storage conditions for the material in plant data/stor. 1 view

Benefits of Automatic Picking Location Determination

Ø  Increased Efficiency: Significantly reduces manual effort and processing time for outbound deliveries.

Ø  Reduced Errors: Eliminates the risk of human errors associated with manual picking location assignments.

Ø  Improved Inventory Accuracy: Real-time updates and tracking of stock movements within the warehouse.

Ø  Optimized Picking Routes: Can be integrated with WM/EWM to optimize picking paths, minimizing travel time for warehouse staff.

Conclusion:

By implementing automatic picking location determination in SAP, we can streamline our warehouse processes, improve efficiency, and enhance inventory accuracy. This blog provided an overview of various methods and steps involved. Remember to tailor the implementation to our unique business requirements and leverage the power of SAP to optimize our warehouse operations.

#Pick Point Determination #Delivery Processing #Shipping Point Determination

#Storage Location Determination

How to fix the quantity on stock in transit when error message "M7 022 - & exceeded by & & &' is raised"

 SAP error message "M7 022 - & exceeded by & & &' is raised"

Issue

Ø  When trying to post a goods receipt for an Outbound Delivery at the receiving plant which was created based on a Stock Transfer Order (STO), error message 'M7 022 - & exceeded by & & &' is raised. 

Ø  Unable to post a Goods Receipt against a Stock Transport Order in transaction MIGO due to error 'M7 022 - & exceeded by & & &'.

 

Reproducing the Issue

Ø  Go to MIGO transaction.

Ø  Select a Goods Receipt for Outbound Delivery / Purchase Order.

Ø  Insert Delivery Number /Purchase Order number, movement type and execute.

Ø  Insert storage location, if required.

Ø  Set item as 'OK'.

Ø  Click on post button.

Ø  Error message 'M7 022 - & exceeded by & & &' is raised.

Ø  Go to VL32N transaction & Enter Inbound Delivery Number.

Ø  Click PGR - Post Goods Receipt.

Ø  Error message 'M7 022 - & exceeded by & & &' is raised.

 

Root cause for this issue.

Ø  Inconsistent quantity on stock in transit: Rounding issues, incorrect sequence of goods movements, etc.

Solution

Ø  How to fix/clear stock in transit?

Ø  For fixing the stock in transit by means of MIGO / VL32N transaction, we should post a stock adjustment by using the movement types '557/558' to clear MARC-TRAME field in MIGO transaction.

Ø  It should be used to fix rounding issues.
If we cannot allocate this cost to any cost center, please go to OMJJ transaction and set cost center field (KOSTL) as 'optional entry' to the affected movement type.

Ø  This option is not valid for Stock Transfer Order-cross-company scenario.

Ø  If the material is split valuated, the system will issue the message M7048. To work around this, you can temporarily deactivate the error by entering ' ' (blank) for this message in the customizing transaction OMCQ .

Ø  For blocking the Stock Transfer Order document by means of ME22N transaction, you should select the affected Stock Transfer Order document line item and click on 'locker' icon (not 'trash' icon).

Ø  It will remove Stock Transfer Order document from MB5T transaction.

Ø  For closing the Stock Transfer Order document  by means of MIGO transaction, you should post a goods issue reversal at the supplying plant to the missing quantity or post a goods receipt at the receiving plant to the missing quantity.

Ø  For fixing a wrong stock in transit created by an inconsistency between EKET x EKBE tables, we should go through the below points a, b & c to fix the inconsistency.

a)      The schedule line quantity is less than the goods issue quantity (EKET-WAMNG) or less than the delivered quantity at schedule line level (EKET-GLMNG).

b)      The goods issue quantity (EKET-WAMNG) at schedule line level differs from the goods issue quantity actually posted (according to the purchase order history).

For standard purchase orders or scheduling agreements, we have the following inconsistencies:

c)      The goods receipt quantity (EKET-WEMNG) at schedule line level differs from the goods receipt quantity actually posted (according to the purchase order history).