Delivery type relevant to MRP

Hi Friends
When we create Stock transfer order, in MD04 the PO and MRP elements appearing for both the plants.(supplying and Receiving plant)
After creating Outbound delivery against PO from Supplying plant the PO (Ord.Ds) is not appearing in the MD04
My issue is the PO has to appear in MD04 untill PGI.
What MRP settings I have to check/Change to solve this.
Regards,
Srihari.M

Srihari,
I am curious as to your reason for wanting to see the STO requirement, when in fact the delivery is the object that is creating the requirement.
I suppose one solution would be not use a delivery at all.
Stock Transport Order Without Delivery - Managing Special Stocks (MM-IM) - SAP Library
When you elect to use STOs with deliveries, in the standard process the delivery requirement replaces the STO requirement in the supplying plant. I am not aware of any standard configuration that would bypass this behavior.
Best Regards,
DB49

Similar Messages

Delivery type "LB" and MRP

Hi All
I work on the APO side and iam not thorough with MM . I have a question about the subcontracting scenario .
We provide components to the subcontractor who then makes the finished products and ships them to our plant. Let us assume we have a subcontracting requirement for 100 CS. We now create a delivery (ME2o) to the subcontractor for 100 CS ( delivery type LB) . When we look at MD04 the delivery created for 100 CS is not offsetting the subcontracting requirement of 100 CS. So we now have a demand of 100 + 100 = 200 CS which is actually not the case. Is this a standard SAP behaviour ?
I believe whenever we issue goods to the vendor the stock at subcontractor location (MatSub) increases and the dependent demand gets offset by stock at subcontractor location . But why doesnt a delivery to the vendor offset the dependent demand ? Please help
Thanks
Saradha

Hi ,
I think planning strategy group plays a role in consuming the requirements along with MRP type (defined at material level)
check out MRP3 view -> Planning , Strategy group.
Thanks,
sudhakar

PR make it relevant to MRP

Hi
1) How to make a particular PR type relevant to MRP.
Where do i need to specify.
2) Can only one PR type only can be created after MRP run MD02 ?
3) Where do i need to include new type PO to appear in MD04 -> Convert Purchase Requisition to Purchase Order.?
Thanks
MM

1) How to make a particular PR type relevant to MRP.
Where do i need to specify.
: Go to the path in SPRO - Production- Material Requirements Planning - Procurement Proposals - Conversion of Procurement Proposals - Define Conversion of Planned Orders into Purchase Requisitions
The various document types can be triggered from the MRP group setting in the system. Search under the MRP group in the system
Here in the
2) Can only one PR type only can be created after MRP run MD02 ?
It is possible in the system. Check the settings under the path goven above
3) Where do i need to include new type PO to appear in MD04 -> Convert Purchase Requisition to Purchase Order.?
Same settings as above
hope this helps you

Question on Schedule Line category in Sales Order not relevant to MRP

Hi experts,
I want to know whether the sales order having any schedule line category like CP, CN, etc will not be relevant for MRP. In other words, If I do the MRP run for the Sales Order Requiremnt having any Schedule Line Category in particular will not generate any procurement proposals like Planned order/ Purchase Requisitions. Please advice me on the same.
Regards
Brijesh

Dear Brijesh,
Please find some info related to scheduled lines below,
The various schedule line categories are controlled in different ways:
The schedule line AT in inquiries is used only for information.
No requirements are transferred and no availability check is carried out for the schedule lines BN and CN.
Requirements are transferred and the availability of the material is checked for the schedule lines BP and CP.
No stocks are managed for the schedule line categories BT, CT and CX. No goods issue is posted for the categories BT and CT. However, goods issue is posted for CX.
The schedule line categories BV and CV are controlled in the same manner as the categories BN and CN. However, requirements can be passed on for analysis purposes.
Goods receipt is posted for the schedule line DN in a returns document.
The schedule line categories CN, CP, CT, and CV are relevant for delivery; the other schedule line categories are not.
*Control Elements for Schedule Line Categories
Different schedule line categories are permitted according to the sales document type and item category you are using. You can use control elements to tailor the schedule line categories to meet the special demands of your installation. You can also define new schedule line categories.
Hope this helps.
Thanks
Murtuza

New inbound delivery type

Hi all,
We have a requirement to create a new PO type and link this to a new Inbound delivery type (copy of EL) as part of a new business process. I am led to believe that this is not supported by SAP. Can any clarify please as trawling OSS has not revealed anything.
Rgds
C

Hi,
also check
Go to SPRO->MM->Purchasing>Confirmation>Setup confirmation control
Select the 10 and check the check box Create inb delivery
then select the line and click on the confirmation seq and make GR relevant, MRP relevant and GR assign (all three box checked)
Process Flow: -
1. ME21N - In PO, Confirmation Tab, select the confirmation control key as "Shipping Notification" or "Inbound Delivery"
2. VL31N - Create Inbound Delivery w.r.t. PO
3. MIGO - Goods Receipt > Inbound Delivery
If you don't select the conformation control key in the PO than system wont allow you to create the Inbound delivery against the PO.
Rahul.

Using Different inbound delivery type?

Dear experts,
In the goods receipts process we currently are using the standard inbound delivery type "EL" with the standard item category ELN, which is not "Relevant for putaway".
We are assessing the possibility of start using WM in one of our plants. So, I found out that the we should be using a item category (in the inbound delivery) with the field "Relevant for putaway" flagged. Like, for example, the standard WIDN (maybe together with the standard inbound delivery type WID). But only at those plants with WM!
The issue is that as far as I know the inbound delivery type determination depends on the "Internal Confirmation Categories":
So for the type "2 Shipping Notification" only one delivery type can be chosen, how are we suppose to do it plant dependent?
It looks like a unique delivery type should be used in the client?
Thanks in advanced,
Fortian
P.S.: I already read SAP notes 214604 & 201655 but they are not being helpful so far... Maybe I'm missing something.

From your post I understand that the current plants are IM managed.
So for these plants the put away relevancy will not have any effect so if you enable the put away relevancy for the EL delivery type there will be no impact on the IM plants and for the WM plant the put away will be relevant.
Now the usage of the put away relevancy will also depend on which transaction you are using for posting a goods receipt. If you post via VL32N then you will first have to perform the put away step and then the GR posting. If you use the MIGO/MIGO_GR transaction then the goods receipt in WM will also be posted before the put away happens.

Output type for Proforma Invoice for return delivery from delivery type RLN

Client require Output type Proforma Invoice for return delivery to vendor. As such return item category is not relevant for pricing so from delivery to proforma invoice can not have with p-ricing. I got quantity correct but pricing is coming Zero.
Client have ZPAC as packing list output type from delivery which shows quantity and pricing. So decided to use the same logic to pull pricing for proforma invoice from delivery.
Here delivery has standard output ZPAC as packing list with access sequence Z002 as Delivery Type.
I want to pop up output type for all return delivery so using access sequence with delivery type/vendor.
Vendor filed does not exist in delivery output type so brought that firld LIFNR.
It is assigned to procedure and maintained ZPRO output type for Proforma invoice. Asigned VV21 on front end.
Problem Still automatic output type ZPRO is not poping up. What type of access sequence will help me to pop up or what in configuration am I miising?
Appreciate help for solution at earliest.

Hi Padamsree,
I know Pricing & output very well. I need profomra invoice to be printed with quantity & value for return goods to the vendor. Pricing is associated with Item category RLLN for delivery type RLL which is return type delivery.
I need to have pricing in my Proforma invoice which is copied from delivery to billing document VTFL. Just check well how it is working in the system & if you know please answer so that it should be workable on the system. As theoretical answer may not be helpful. Appreciate for your time.
Thanks

Request delivery schedule with fixed total delivery qty updated by MRP

Hi Gurus,
Please help on this issue. The issue is since in the "direct Purchase order", the delivery date is fixed & not updated by MRP, seems only delvery schedule line in Scheduling Agreement can be updated by MRP.
Below is the requirement:
1) Use appropriate Purchase Document (like Scheduling Agreement) for subcontracting the in-house production parts when capacity is insufficient, so that delivery schedule qty can be updated by MRP.
2) The Purchase Document will covered partially the requirements of the in-house production parts, the qty covered should be the same as total open qty in the Pur Doc to be delivered (if it's Sch. Agrmnt, should be Target Qty)
3) During MRP run, source of supply should be assigned to the Purchase Doc iteam firstly, afterward assigned to planned order
Thanks a lot!
Jerlyn

Hi,
For all of your queries;
ME01 - Maintain Source List for the materials
Here maintain, Vendor, Plant, Purchase Org, most important input Scheduling Agreement No in Agreement column and in "MRP" column, use "2" i.e. Record relevant to MRP. Sched. lines generated automatically
Now run MRP and observe the result, it will consider Scheduling Agreement in MRP.

Problem with Delivery Type Determination in Purchase Order

Dear All,
We are working on a IS-Retail Scenario where we are dealing with generic articles. While creating a PO, we have encountered an error which says:"Also specify a delivery type in case of shipping data relevance". The error message number is MEPO 099. We have checked that Delivery type NL is attached to the document type under the supplying site customizing, and supplying site is attached to the receiving site with the correct document type. Can anybody throw some light on what we might be missing out in this scenario?
Thanks and Sincere Regards,
Amitabha

Hi
I suppose you are creating a retuns PO ,
Please maintain the customizing of the same in SPRO-> MM -> Purchasing-> Purchase Order-> Returns Order-> Store Return / Return Plant to Plant
here you need to maintain the delivery type for returns.
This message is trigerred only in case of Returns order
In SAP Retail, plants are referred to as distribution centers or stores. With store returns, you can map the return delivery of goods from
a store to a distribution center (this is the most common case),
from one distribution center to another distribution center,
from one store to another store,
from a distribution center to a store (although this is not very common).
Requirements
For the return delivery types, you have to make settings for the item category determination.
Partner schema must be assigned to the return delivery types.
The relevant goods movement types must be assigned to the schedule line categories (for the returns in Sales). The following schedule line categories are also available in the system:
NR - Replenishment Returns and
NS - Replenishment Cross Company Returns
Activities
Assign the required return delivery type to
purchasing document category F (purchase order),
purchasing document type (NB - standard purchase order, UB - stock transport order),
the supplying plant (the one to which the goods are being returned)
The following return delivery types are available in the system:
NLR - intra-company-code store returns (purchasing document type UB for replenishment and return orders, delivery type NL for the replenishment delivery)
NCR - cross-company-code store returns (purchasing document type NB for replenishment and return orders, delivery type NLCC for the replenishment delivery)
Please maintain the required customizing
Thanks & Regards
Kishore

Several Inbound Delivery types in one plant?

Hi Guru´s,
1. Is it possible to have several inbound delivery types and also to be able to use all inbound delivery types in one plant at the same time but in different process?
E.g:
1a. I have plant with a sloc and WM connected which I would like to have inbound delivery with picking connected to it
1b. I have the same plant with only sloc connected and would like to have inbound delivery without picking and confirmation of the inbound delivery to be set (PGI)...
2.Is above scenario possible to have?
3.If please guide me on how the correct way is to have this set up because I´m stuck...
4.If not please explain why it is not possible or....
5.Is there anouther way of doing it due to we would like to have the same process in every warehouse...
Thank You in advance to clear things out for me!
BR,
Christian

Hello Christian,
Yes it is possible to use delivery types based on your requirements as mentioned by you.
You will require to customize following things ;
Define delivery Type
SPRO>>Logistics Execution>>Shipping>>Deliveries>>Define Delivery Types.
You can use standard delivery type and create new customized ones by copying them.
Define Item categories for deliveries
SPRO>>Logistics Execution>>Shipping>>Deliveries>>Define Item Categories for Deliveries
Once item categories are defined, you have to assign the item categories to relevant document types.
Now you have to customize for picking and packing control
Picking control;
SPRO>>Logistics Execution>>Shipping>>Picking>>Define Relevant Item Categories
Packing control;
SPRO>>Logistics Execution>>Shipping>>Packing
Br,
Tushar

When creating Outbound Delivery, how does SAP propose Delivery Type?

Hi,
in VL01N, when i create an outbound delivery i can create it with reference to an SO or without reference to an SO.
But how does SAP know the delivery type to use?
I don't know where to really look.
in SPRO i went to:
Logistics Execution ---> Shipping --> Deliveries
but all i saw was delivery type definition.
then i went down the path:
LE --> Shipping --> Copy Control --> Specify Copy Control for Deliveries
then i found a table linking Sales Order Types and Delivery Types.
However, we use SO doc. type Z*** for example but I see that there are multiple entries for it linking to various delivery types including LF and another custom Z*** delivery type.
My question is, how is the system choosing which delivery type to use?
Is it maintained in customer master or at config level?
Thanks.

Hi Gavin,
If you check VOV8 for example standard order (OR), the delivery type is LF. Here you can define only delivery type person SO. Hence you will not find SO to LF relation as 1:N but will surely find N:1.
Item category just defines the billing relevance of the item. Hence if billing is delivery related then delivery will be created for the item.
Now once order is created when tried to deliver, it will know that LF is the delivery type from VOV8 and from item it will know he should deliver it or not.
Hope this is clear now. Reward if helpful.
Kind regards
sandeep

No reservations relevant to MRP exist for project

Hi all,
While doing MRP for WBS through MD51 i have got an error " No reservations relevant to MRP exist for project " . I am not getting where the problem is occurs.
Regards,
Swapnil Vaidya

Dear .
1.Please check wether in your project builder(CJ20N) Project Status is REL and Procurement Type is :Reservation for WBS element . then it will not create this masg.
2.Check whether MRP run date is after the project start date as well as the WBS element is also with in the time frame
3.Check the material master parameters(MRP1-MRP4 view ) for Project material which are to be planned by that Project WBS .
Check and revert
Regards
JH
Edited by: Jiaul Haque on May 1, 2010 2:27 PM

Steps to define new delivery type

Hi ,
I want to know that,what is the complete step to define the new delivery type ,that can be use in exsiting order type to complete the sales cycle process.
Regards
Prabudh

Consignment Stock Processing:
Consignment Stock Processing
Purpose
Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.
Consignment Fill-Up: Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.
Create a sales order using order type KB.
Enter the required data on the customer, the consignment goods and the delivering plant.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The underlying goods movement type is a stock transfer. This ensures that when goods issue is posted, consignment special stock is created for the customer concerned. If special stock of this kind already exists in the delivering plant for this customer, the goods are posted to this special stock.
Order type: KB (document category C: sales order)
Std. Delivery type: LF
Item category: KBN (not relevant for pricing and billing)
Schedule line category: E1 (relevant for deliveries, uses availability check, 631 (GI consignment: lending) to post the stock into a special consignment category in the delivering plants stock for that particular customer and material)
Copy control rules for the sales doc, item category, and schedule line category.
Use trans MB58 or MMBE to check the stock.
Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.
Create a sales order using order type KE.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The goods are then reduced by the relevant quantity in the special stock assigned to the customer. This goods issue also reduces your total stock.
Invoice the delivery which issues the consignment goods.
Order type: KE (document category C: sales order)
Std. Delivery type: LF
Invoice: F2
Item category: KEN (relevant for pricing and deliver related billing, special stock indicator W, should determine cost too)
Schedule line category: C1 (relevant for deliveries, uses availability check, 633 (GI issue: customer consignment)
Consignment returns: proceed as follows: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.
Create a sales order using sales order type CR.
Enter the required data on the customer and the consignment goods.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The goods issue posting cancels the goods issue posting which was carried out when the consignment goods were issued. This posting records the return of the goods to the plant where goods receipt was carried out.
Create a credit memo for the consignment return you created in Step 1.
Order type: KR (document category H: returns)
Delivery type: LR
Credit for Returns Order type: RE (delivery or order related billing)
Item category: KRN (relevant for pricing and deliver related billing, special stock indicator W
Schedule line category: D0 (relevant for deliveries, no availability check, 634
Consignment Pick-Up: The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.
It may be beneficial to have a mandatory reference such as the consignment fill-up. In addition to it copy control rules can be used to further control it. In the copy control rules indicate the document flow. As the stock is coming back into the warehouse or plant, you can specify a returns shipping point to be automatically determined. No invoice is necessary, as the goods are not changing ownership.
Create a sales order using order type KA.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The transaction is completed by the goods issue posting which initiates a transfer posting from the customer's special stock to your plant stock.
Order type: KA (document category C: sales order)
Delivery type: LR
No invoice
Item category: KAN
Schedule line category: F1 (relevant for deliveries, availability check against the stock on the customers consignment, 632 (Consignment pickup)
Reward points if useful
Re: Delivery Document Type
Re: Consignment Process

Issue while posting using goods issue for delivery type NL

Hello Experts,
I have created an outbound delivery for an intra-company transfer (within same company code) between two plants. The delivery type in NL (replinishment delivery)
When i am trying to post the goods issue from supplying plant, I am getting following error
"Account type K is not defined for document type WL".
Delivery type NL should not be used to issue stock to vendor but I am not issuing it to any external vendor , issuing the stokc only to a receiving plant.
Please help to understand why i am getting this error.
Regards,
Nish.

Hi,
If you are doing an STO Scenario, Check whether you have created the supplying plant as a vendor.
The Vendor Account group should be plants.
Also check whether you have given the plant in the vendor master Purchasing Data - Extras tab in the menu click on add purchasing data & check.
If you haven't assigned this, do the same & create a fresh STO & check.
Hope it will work.
Thanks & Regards,

Fetch Top level WBS elements for delivery type LP

Hi everyone,
we are working on a delivery analysis report and we are in progress of fetching sales order number for deliveries with delivery type LP.
How we are doing?
so we are fetch the UP values from PRHI table for the wbs elements in LIPS.
Now we need to fetching the top level wbs elements from PRHI table by passing the UP values to the same table until the UP field value becomes initial.
Then fetching the corresponding sales orders from the VMPA table for the wbs elements from PRHI table for the value of corresponding UP field is initial.
So it is going through so many iteration to fetch the UP value again and again until it is initial.
What we need?
So if someone can suggest a FM or method to fetch the top level WBS element for the given WBS element from LIPS table will be of great help.

Hi,
Try FM
'BBP_PS_PROJECT_GET_LIST
'BAPI_PROJECT_GETINFO

Delivery type relevant to MRP

Similar Messages

Maybe you are looking for