SAP Mental Notes » SD

Batch determination for IM

Kowboy — Fri, 06 Feb 2009 08:31:53 +0000

This blog offers a quick guide on how to use standard SAP Batch Determination for a material transfer. For an internal goods movement we need SAP to pick the batch from stock with the earliest Shelf Life Expiration Date (SLED). We don’t want our fresh products terminate themselves from stock…

1. For this we will be using standard IM search strategy ME001 – Standard Search Procedure.

IMG > Logistics > Batch Management > Batch Determination and Batch Check > Batch Search Procedure Definition > Define Inventory Management Search Procedure

IM Search Procedure

The search procedure consists of three condition types that is plenty to us. We want the determination rule to be activated when we use Movement type 311 (Mvt from SLoc to SLoc) in Plant X for only a specific material. ME01 condition seems to fit this purpose.

2. Now we need to activate the search procedure for the movement type, otherwise it will not even begin to look for a determination procedure in the first place.

IMG > Logistics > Batch Management > Batch Determination and Batch Check > Batch Search Procedure Activation and Check Activation > Allocate IM Search Procedure/Activate Check

Activate procedure

We add the Search procedure to movement type 311 and check the check box so that manually entered batch codes are validated as well.

3. Next we need a sort rule to be able to sort batches on SLED.

IMG > Logistics > Batch Management > Batch Determination and Batch Check > Define Sort Rule

Sort rule

For the rule we use standard Batch Characteristic LOBM_VFDAT. This is the SLED. We need earliest batches first so we choose ‘Ascending’.

Now we did all necessary customizing. It may be necessary to create batch classes with classifications if you are not already using this. If your products are batch managed already, your materials should already be assigned a batch class in the material master. This class we will also be using in the batch determination.

4. The last step is to create a search strategy, much like message determination for document output (if you never did this, then never mind this comparison).

SAP Menu > Logistics > Central Functions > Batch Management > Batch Determination > Batch Search Strategy > For Inventory Management > MBC1 – Create

We will use strategy type ME01 and key combination Movement Type/ Plant and Material. Remember that we want the search procedure only to work for one material at time of goods transfer in one plant. If you want you can extend the procedure to all materials for movement type 311. In this case choose key combination: Movement Type/Plant. It’s that easy.

MBC1 - Create Search Strategy

Here we actually enter the criteria when the batch determination should be activated: movement 311, material MRP and plant 3000. You can choose settings with regards to batch splits and whether determination should occur in dialogue mode or background. For details F1 your way through these options.

Last but not least: enter Selection criteria and Sort rule by pressing the buttons in the task bar. For selection criteria you can e.g. say SLED > 01.01.2009. It is a minimum requirement that the procedure needs. Be selecting a SLED date in the past I’m assuming that all batches are in scope (at the same I assume that expired products are taken off the shelf in time so I will not use it in my delivery process).

I will use the sort rule I created in the previous step: sort by SLED.

That should do it.

Kowboyz BV / CC BY-ND 3.0

Unblock SD Documents

Kowboy — Fri, 23 Jan 2009 13:29:36 +0000

This post is an extension to a previous post on Credit Checks exceeded. When you are in a testing environment it is common that it’s difficult to quickly process sales orders and/or deliveries because the credit check is exceeded for a customer. Credit is building up, since so many sales orders and deliveries are entered but are usually not going through the whole process including payment processing. To quickly clear a blocked order got to transaction VKM1.

VKM1 - Blocked SD Documents

In the main screen enter a common criterion like Credit account (usually sold-to) and hit the execute button (F8). In the report screen that follows, select the document to be unblocked and press the green flag button followed by saving the approval. Now you can continue processing the order or delivery.

Kowboyz BV / CC BY-ND 3.0

Exclude storage location from ATP

Kowboy — Thu, 04 Dec 2008 10:15:23 +0000

In some cases it may be necessary to exclude a storage location from ATP (and MRP). This is often the case at companies who e.g. keep inventory on materials that are stored in a well-sized showroom. How you can block a storage location for MRP, I explained in an earlier post. This will give you some pointers on blocking for Available-to-Promise.

Unfortunately there is not a simple switch per storage location to block for ATP, as there is for blocking for MRP. So we are looking for alternatives:

Often the stock can be put on ‘blocked’ or ‘restricted use’ stock status. Usually this stock is excluded from the scope of check for ATP on Sales Orders and Deliveries. Otherwise this can be adjusted.
OVZ9 - Scope of Check
If the previous REAAAALLY doesn’t work for you you can look into EXIT_SAPLV02V_002 for Storage Location Determination. This exit is designed for deliveries and is not easy to implement. Just look at note 415716. Personally I like to stay away from implementing exits that come with pages of notes and disclaimers. But don’t let me hold you back.

If your stock is so special that it shouldn’t be included in ATP, the first option should oftentimes do it for you. It requires that procedure for receipt of goods in this storage location should be slightly adjusted by posting it to special stock instead.

Different planning views

Kowboy — Sun, 16 Nov 2008 15:47:31 +0000

End-users can get confused about the difference between MD04 – Stock/requirement List and MD05 – MRP List. This post will give you the answer on when to use what report and why:

MD05 will show only the situation as it was since the last MRP run. This transaction is suitable for reviewing the MRP run. Without taking into account new stock issues or receipts MD05 is ideal for evaluating your MRP parameters. Look at the stock date, this is the date of the last MRP run.

MD04 will show you the current stock situation taking into account all requirements and planned receipts. The stock date is always current (=today). This view is appropriate if you make procurement decisions in dynamic environments, i.e. requirement situation changed a lot since the last MRP run.

Example: MRP has run for a material on Monday early morning. The planner will not evaluate the procurement proposals until Monday afternoon. Customer service entered a large number of sales orders in the system, and the warehouse already shipped quantities. In this case I suggest the planner uses MD04 to get the most up-to-date planning situation. On top of that I would actually recommend the planner gets out of bed early and does the planning evaluation first thing in the morning. If a planner allows a lot of changes to happen, the procurement proposal out of MRP may not make sense anymore.

I will post an article on the workings of SAP MRP and the theory of MRP in the future.

Kowboyz BV / CC BY-ND 3.0

Sales Order requirement date to MRP

Kowboy — Tue, 28 Oct 2008 21:04:28 +0000

I’m working in a business process where a sales orders requirement date should never be transferred to MRP with the original customer’s requested date.

Example: at the time of order entry ATP bounces the requested delivery date, since product is not available at the time. The system suggests a new date for confirmation. The customer at this time has the option to agree to the new proposal or a sales order will not be entered. I want this new committed date transferred to MRP.

To do this I select the ‘Fixed date and quantity’-indicator in the Schedule lines tab in VA01. As in my case this should always be the case, in customizing I choose this as a default setting for the specific SalesArea (IMG > Sales and Distribution > Basic Functions > Availability Check… > Availability Check > Availability Check with ATP… > Define Default Settings)

VA01 - Fixed date/qty indicator

Without setting the indicator you are basically suggesting that production can still catch up with this additional requirement and the customer’s original requirement date will be transferred to MRP. See also SAP Help.

Kowboyz BV / CC BY-ND 3.0

Credit Check Config Reports

Kowboy — Tue, 28 Oct 2008 20:59:23 +0000

Using a test environment that is due for a refresh I run into credit limits when entering sales orders more than often. Manipulating the credit check for a customer in FD32 is not always sufficient. The following reports also are useful (if not essential):

RVKRED06 - Background jobs for checking blocked credit management.
If an order is no longer outside the horizon as defined in the dynamic credit check, (i.e. it is INSIDE the horizon) it can cause existing “good” orders to block. If you run this job every night, if you have your horizon set for 1 month it can cause a lot of blocks at beginning of month. Try to use ‘W’ for weekly horizon status.

RFDKLI10 – Customers With Missing Credit Data

RFDKLI20 – Reset Credit Limit for Customers

RVKRED77 – Reorganize SD credit data
When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.

RVKRED08 – Checking sales documents which reach the credit horizon
You should runs this report periodically, usually at the start of a period. The report checks all the sales documents, which reach the dynamic credit check horizon. The period for the ‘date of the next credit check’ is proposed from the current date, with the help of the period split for open sales order values.

(Courtesy of SAPTechies)

If you prefer the quick way of unblocking the one sales document go to this post.

Recovery of SD requirements for MRP

Kowboy — Tue, 28 Oct 2008 12:22:12 +0000

At some point in time sales and delivery requirements may get out of sync due to maintenance resulting in planning errors. Usually these errors are found when going through MD04. You will typically find deliveries (collective requirements) that cannot be traced back to original delivery documents.

The proper solution for this is to run report SDRQCR21 (via SE38):

Program SDRQCR21

select the material and plant you wish to run the correction;
select the option data transfer when you actually wish to run the correction on the database;
select compare always in order to improve performance. Without selecting this the whole database for material/plant will be regenerated;
select planning entry to ensure the material is included in the next MRP run;
the option Processing per material results in a different log.

After this your MRP overview should be back in sync.

EU membership

Kowboy — Sun, 26 Oct 2008 19:34:28 +0000

Sometimes it may be necessary to build a custom solution to check the European Union-membership status of a country. For example for tax purpose you want to identify on the basis of sold-to whether the customer is in the EU. Check the country code from the address of this customer with the EU membership field (XEGLD) in T005 .

No related posts.