Bill material in SD and MRP

Hello,
We are working with MRP and transfer order between plant (UB) and I have one question.
We have a shop, and It sold 5 unit of material A, then we execute the MRP, the normal is the automatic creation of the purchase order request (trasnfer UB) to sent material to the Shop from the warehouse.
But we want the following behavior: if the Shop Sold 5 units of A, and I Execute the MRP, the result should be the creation of the purchase order request but with 5 unit of the material B.
It's posible to create a Bill of material in CS01, to change in the MRP or transfer order the material A to the B.
Best regards and thanks
Javier

Hi,
Thanks for your help,
But I change the item category of A to LUMF, B continue with NORM.
I create the BOM, for the material A:
Material A
Center Z005
BOM USAGE: 3 universal
item 10 L material B quantityt 1
then I have check the item category asignation:
ZTA LUMF TAP TAQ
ZTA LUMF TAP TAN
And when I create the sales order with material A, nothing happens.
I will continue testing if you detect anything in my comments let my us.
Thanks

Similar Messages

Billing Document and Material Document number and Date (Goods Issue)

Dear Experts,
Is there a way I can find the relationship between a billing document and a material document number and Goods issue date?
Thanks

Hi Abid
Is there a way I can find the relationship between a billing document and a material document number and Goods issue date?
You have to follow the flow from the billing document to the material document. This will only work if the billing document comes from a delivery note.
Billing document => Delivery
LIPS-VBELN = VBRP-VGBEL
and LIPS-POSNR-VBRP-VGPOS
So you have LIPS + LIKP with the LIKP-WADAT_IST as the goods issue date.
Delivery => Material Document Number
You can use the table VBFA with the delivery item as the preceding document number (VBFA-VBELV) and item (VBFA-POSNV) ; you will also have to define the preceding document type as J (delivery) and the document category of subsequent document as R (material document).
Because in SAP nothing is simple, there might more than one material document, because the goods issue (601) movement might have been canceled and issue again. So you will have to decide what to do in that case.
Best Regards,
Franck

Item category (Customized )ZJT1 and MRP type for material is not allowed

Hi Guys,
When i try to create the order i see the error as item category and MRP type of the material is not allowed.
I checked in Vov5 table, i could observe that Schedule line category is maintained.
Could you please help us in resolving this..
Thanks and regards,
Rahul

Hi,
Please assign the Item Category ZJTI and MRP type (for eg: PD) assigned to the schedule line category in IMG under Sales and Distribution--> Sales ---> Schedule line -->Assign schedule line
Hope this resolve your issue
Regards,
KrishnaO

Item Category and MRP type for material is not allowed

Hello all,
I got a Error Message:
Transaction Z113 is not defined (Message no. V1347)
Diagnosis
This combination of item category Z113 and MRP type for material is not allowed.
System response
The system does not allow further processing of this item.
Procedure
Check your entry.
You can display the combination defined in table TVEPZ, which controls scheduling line category determination, and change it as required if you have the authorization to do so. The MRP type for the material may be changed in the material master.
The SD Configuration seems all right, I have:
Sls Doc Type (VOV8) ZA9 (no delivery type assigned)
Item Category (VOV7) Z113
Assigs Sls Doc & Item Ctgry (VOV4) ZA9/ZNOR/blank/blanl/Z113
ZNOR = Std Item-Av. chck Del
ZNOR defined in MM03/Sls Org 2
Define Schedule Line (VOV6) = Z7 (without delivery)
Z7 has FLAG on Prod Allocation
Assign Schedule Line (VOV5) = Z113/ND/Z7
At table: TVEPZ
I have the entry: Z113/ND/Z7
Guys, what would?
Please help me out because I am stuck in this issue.
Thanks a lot,
Barbara

Barbara, this may be tied to Strategy Group on the Material Master (I can't read enough into the detail)
Item Category determination + MRP Type for your schedule line type ties to a Sched. Line category(this you know)
New Rqmts class gets tied to a Rqmts Type
New Rqmts Type gets assigned to rqmts class
Strategy, assign the Rqmts Type to it
Strategy Group, Assign the Strategy to it
MM02 [MRP3 view] strategy group should be the one that ties together (all the other ties
It may be something in this area that you need to trace through ?
Bill

Material Availablilty Date and Open Billing

Hi All,
Can you please tell me what is material availablilty date and Open billing.
In which table we can find these fields. We want to add in VKM4.
Regards,
Isha.

Hi Isha,
As Ravi said, you can found Mat.Avail.Date in table VBEP, the feild name is MBDAT.
When system check the availability then there are some steps which system follows like before delivery --> what is Good issue date --> before that what is transportation planning date --> before that what is loading date --> before that what is material availability date
so system 1st take material availabilty date then step by step, finally it declares the delivery date.
System But as per my knowledge "Open billing" is not suppose to be feild, It should be a status in any table like In VBUK, VBUP, VBRK
Hope this helps,
Regards,
MT
Edited by: M T on Feb 24, 2010 12:13 AM

Significance and use of CVD indicator and MRP indicator in J1IEX

Dear Frndz...
Plz expln significance and use of CVD indicator and MRP indicator in J1IEX.
Regards,
Amit P Hiran
njoy SAP..
njoy Life...........

hi
>CVD TICk
CVD indicator will be auto ticked when when u go for IMPORT PROCESS
check folowing for import process
import process customization
>MRP TICk
MRP tick is used for the first stage dealer scenario ,where at time of purchase u cant have excise values
the bill will be including base price exciseothertax + delears commisiion
E.g.:
Material Price = 80/-
Excise Duty = 14/- (BEDECessSECess)
Margin = 6/-
Total =100/-
VAT @3% = 3/-
Grand Total =103/-
Step 1:
Create PO with Base Price as 100/- by selecting tax code which is having VAT as 3% (Total PO value will be 103/-)
Step 2:
Post MIGO and Capture Excise Part - 1
Click on More details icon in Excise tab (header), check MRP Indicator in miscellaneous tab, Enter Assessable value as 80 in Excise tab Item level and enter the excise values BED, ECess , SECess manually, check & save the document.
Step 3;
Post Excise Part 2 in J1IEX
Step 4:
Post MIRO by checking calculate tax, edit base value as 80/- enter the amount in header as proposed by the system (103/-), simulate & post the document.
Note 1104456 - Use of MRP indicator for capturing excise duties from dealer

Raw material planned cost and qty in table MCKALKW

Hi,
Raw material planned cost and quantity in table MCKALKW is not equal to cost analysis in CO01 / CO02.
Could you please let me know how to get the planned cost and quantity for production order components for report development. i checked other tables like AFPO and AFKO and it is showing only for main material and not for its compoen

Hi,
You can check the cost of the individual components in Bill of materials of each material seperately. Hope this works for you.
Thanks and regards,
Murali krishna Maganti

MD04 Transaction and MRP related queries

Hello All,
i have some specific questions regarding MD04 and MRP Run
1. In MD04 for few raw material i am getting -ve available quantities , i am not getting why MRP didn"t run for the same before available qty become negative , we have a batch job schedule for MRP run .
what all the possibilites of not running the MRP ,
We don't have reorder level planning ! MRP type`is standard one PD .
2. For some material we are not able to create a planned order, settings in Material Master MRP view is fine as we have another material with same settings are working , i am running the MRP through MD41 Transaction code >
Forecasting is done through MD61/62 active indicator ticked >
what else could be the reason .
Secondly one silly question does MRP take into consideration available stock during run , i mean if i run the MRP for a material with Tcode MD41 , will MRP create Planned orders , even if enough stock is available >
Thanks for coming back in advance .
Thanks and regards

Look for the MRP list as well (MD05), not only the Stock/Requirements List (MD04).
You can see there the date and time of the last MRP run, and if there was a termination that did not allow the proper run.
There may be a number of reasons why a material was not included in the MRP run, like what type of run (e.g. regenerative or net change), etc.

Cancel Billing ,Material Document(PGI),Delivery,Sales order

hi experts,
pls help me Cancel Billing ,Material Document(PGI),Delivery,Sales order.
so when ever given to billing number cancel to all the document
plz send to me code and suggestions.
plz it is urgent.
advanced thanking you.

you can do that from VF02 - application menu - billing document - cancel.
if you want to do that from program use standard bapi's to cancel BAPI_BILLINGDOC_CANCEL1... also please reffer to transaction code BAPI for more bapis to reverse pgi - or you can write a BDC to reverse pgi - tcode is vl09.
i dont think you cancel order but you can delete depending on your config. check out in application menu on va02. use bapi BAPI_SALESORDER_CHANGE to reject the items in sales order.

Study material on ALE and IDOCS

Hi
If anyone has some study material on ALE and IDOCS ,if you can please send it across to me , it would be very helpful to me .
My mail id is : [email protected]
Thanks in advance
Ankit

1. What is ALE?
Application Link Enabling (ALE) is a set of business processes and tools that allow applications on different computer systems to be linked. This can be done between different SAP systems as well as between SAP and non-SAP systems.
In a single SAP system different applications are integrated via a single database (e.g. finance, sales, production, human resources). However, many companies do not have just one integrated system but a distributed environment with different applications running on different systems. To run the whole business in such an environment the distributed applications have to be linked. This can be done through Application Link Enabling (ALE).
ALE provides distributed business processes that can be used to link the applications on different platforms. There are some ALE business processes delivered in the standard SAP system. Furthermore, there are tools that can be used to change the existing ALE business processes or to implement new distributed business processes.
Besides the business processes there are special ALE services that are required to set up and control a distributed environment. These services include a distribution model, business object synchronization and tools for monitoring or error handling.
ALE is a major part of SAP's Business Framework Architecture. Besides the basis middleware, that provides the communication between components, and the interfaces (BAPIs), ALE business processes and ALE services enable the cooperation of the single components within the framework. That makes ALE the glue of the Business Framework.
2. What are the benefits of ALE?
With ALE companies get the opportunity to improve business performance and to solve organizational or technical issues.
Through distribution you can decentralize your business, enabling local units to operate independently from each other. This flexibility enables the local units to return better business results than in a centralized environment. They have the necessary flexibility to optimize business processes in different organizational units and can ensure that information systems can handle the speed of change in rapidly expanding markets. Distribution allows a high level of freedom, provided that this level of freedom has been clearly defined.
On the other hand, some companies, that already have a distributed organization with different computer systems in the local units, have the opportunity to link their units through ALE business processes. This enables them for example to provide a 'one face to the customer' approach. Another area that can benefit through ALE are virtual organizations (partnerships between independent companies, joint ventures and mergers and acquisitions).
Of course, in many cases an integrated solution based on a single system is not possible at all. Some applications used by a company can not run on the same computer system. This includes legacy systems or complementary software. It may also be possible that a company uses different SAP industry solutions or specific country solutions, which do not run on the same SAP System. If these applications run on different systems they can not be linked by a central database but have to use a special integration mechanism like ALE. In this way ALE also links SAP Core Systems to other SAP components like CRM, Business Information Warehouse or APO.
Besides the benefits of having an improved flexibility in setting up the whole business processes, ALE may also reduce costs, in particular costs of upgrading. If the whole business is run on one integrated system you have to upgrade the whole system, even if only one part of your company (e.g. human resources) requires an update. So the entire company is affected by the upgrade project and all users have to be trained for the new release. Within a distributed environment with release independent interfaces, like those provided by ALE, you can focus the upgrade project on that part of the company that has to be upgraded. The other parts of the company are not involved and need no training. This can save a lot of money. Furthermore, existing investments are protected.
Another cost factor for distribution might be communication costs. For an overseas connection it can be more expensive to provide online access to one central system (T1) than to connect distributed systems to each other (64K line).
There might also be some technical reasons for distributed systems. If some parts of the business have special requirements for security of data access (e.g. human resources), this can be set up much safer on a standalone system, which is, however, linked to other parts of the company through distributed business processes. A similar example is high availability. High availability is usually required by the operations part of the company (production, logistics) but not by other areas (e.g. financials, human resources). In a distributed environment high availability can be set up for specific parts of the environment instead of for the whole business. This can also reduce costs.
In a distributed environment you can not decrease the overall workload of the systems but you can separate the user workloads on different systems. Through this scalability you can improve performance. Another benefit of distributed systems is that if a technical failure occurs on one system, all other systems continue to operate. Only a small part of the business is disrupted by the error. On one central system such an error would disrupt the entire business.
3. When should ALE be used?
Besides the benefits of ALE there are also reasons not to distribute:
The functional scope in a distributed environment is restricted. Not all functionality that is available in an integrated SAP system can be used with distributed systems in the standard yet. Although ALE provides tools to create new ALE business processes or to enhance existing business processes, this does involve additional expenditure.
Each company needs some organizational standards and data harmonization. In a distributed environment less standards are required than on a single integrated system. However, in a distributed environment the maintenance of the standards and the data harmonization is more difficult than on a single system.
The administration of decentralized systems is more expensive. Support and service costs for hardware and software in decentralized systems are higher than these costs in a single centralized system.
ALE should be used in a company if the benefits of ALE for this company outweigh the reasons against distribution. For this you always need to carry out a company specific investigation, in which you also should consider the culture of the company. ALE is good for some companies but not for all.
4. What is the relationship between ALE and Middleware?
Electronic Data Interchange (EDI) is a term for the transfer of business messages between two systems. There are many such messages, the most common of these include a customer sending a purchase order message to a vendor, or a vendor sending an invoice message to a customer. Classic EDI is mainly restricted on the exchange of transactional data, no master data or configuration data. In most cases, EDI replaces the transfer of paper copies of these documents. Via the messages ALE business processes can be implemented between business partners. The EDI messages also use the ALE services.
For the communication between different types of systems special EDI messages are defined as standards for inter company communication. There are many standards for these messages - in the United States, the ANSI X.12 standard is the most prevalent, in Europe, the UN/EDIFACT standard is used. For sending EDI messages the information has to be converted into an EDI standard. With SAP systems this is done by EDI subsystems. This conversion is the only difference between EDI messages and other messages used in ALE business processes. The processing of these messages on the SAP System is the same as the processing of other ALE messages.
5. Which ALE business processes are available?
IDoc Types - Message Types
ALE business processes are integrated business processes that run across distributed systems. This can be two different SAP systems, links between SAP and non-SAP systems, SAP and Web-servers (Internet Application Components) or SAP and desktop applications. The links between the systems may be loosely (asynchronous) or tightly (synchronous) coupled. These business processes are release independent and can run between different release levels of the systems.
Many SAP applications offer ALE distribution processes. The following list gives some examples:
Master data replication (IDoc Types - Message Types - Master Data)
- Material
- Customer
- Vendor
- General Ledger accounts
- Bill of materials
Accounting (IDoc Types - Message Types -Accounting Business Processes)
- Links to logistic systems
- Distributed financial accounting
- Distributed cost center accounting
- Distributed special ledger
- Profitability analysis
- Distributed profit center accounting
- Consolidation
- Treasury
Logistics(IDoc Types - Message Types - Logistics Business Processes)
- Reallocation of materials
- Distribution of sales and shipping
- Product data management
- Purchasing contracts
- Sales and operations planning
- Warehouse management
- Links to warehouse control systems
- Links to production optimization systems
- Links to transport planning systems
Information systems (IDoc Types - Message Types - Logistics Business Processes)
- SAP Business Information Warehouse (BW)
- Exchange of data between information systems
- Web reporting
Human resources (IDoc Types - Message Types - HR Business Processes)
- Human resources as a single component
- Payroll results
- Travel expense accounting
- Links to time collecting systems
However, these standard solutions may not fit 100% for a company. There may be differentiation in the business process or a required distributed business process is not supported in the standard. If this happens, ALE provides tools that can be used to adapt a standard ALE business process or to create a new distributed business process.
6. Which ALE services are available and what do they do?
To integrate distributed systems you need more than a communication infrastructure and interfaces. Some additional services are required that are provided by ALE:
Business process harmonization:
Within system overlapping business processes multiple functions running on multiple systems are involved and connected through multiple interfaces. The processes are combinations of functions (sub-processes) running on the single systems.
(Example: A business process for customer order management involves functions in sales, manufacturing, warehouse management, finance, and so on. It is possible that the sales functions are carried out on another system than the manufacturing, the warehouse management or the accounting. Furthermore, some information exchange with the customer, a supplier or a bank may be involved in the process.)
ALE helps to coordinate the whole business process by defining it within a global model. In this model the business rules for the distribution are defined. Via the model the sub-processes get to know which part of the overall process they have to do themselves and when they have to pass the process over to another system. Through this the whole business process gets harmonized.
Receiver determination:
For distributed business processes a sub-process on one application (client) has to start another sub-process on another application (server). It is important that the new sub-process is started on the right server. Which server is the right one can not be defined by technical values, it depends on the business content of the process.
(Example: A sales system forwards customer orders to two different production systems. To which system a special sales order is forwarded depends on the entries in the sales order (this may depend, for instance, on the ordered material or on the customer). One sales order may also be split into two or more different orders that may be forwarded to different production systems.)
To notify the client which system is the receiver of the communication (server), ALE uses a distribution model. From this model the applications get the information about the right server. There are special ALE BAPIs and function modules available for this. The receiver determination makes sure that the information is sent to the right places.
Business object synchronization (semantic synchronization):
If business processes run across distributed systems, they have to share some data to be harmonized. This is data like business information data, master data or customizing data. If this data is changed in any of the distributed systems, other systems have to be informed about the change. There has to be some kind of subscription of the data.
ALE provides a special service for this data synchronization. This service can detect data changes and distribute the information to those systems that need to know about the change. This service also defines which data is shared. You can determine which fields of a data object shall be common and which fields may vary locally.
Consistency checks:
For a business process running across two distributed applications there has to be some harmonization of the sub-processes in the single applications. For making sure that the sub processes are harmonized there are special ALE consistency check tools. These tools help to find and repair inconsistencies. By this it can be ensured that the whole ALE business process works in the right way.
Monitoring:
For the monitoring of distributed processes it is not enough to monitor all activities on the single systems. The overall business process has to be monitored. The ALE monitoring services provide detailed information about the communication process, the sub-process on the other systems and its results. Database links are created between the business objects in question on the client and the server. This is especially important for loosely coupled applications with asynchronous links. In this case the server can not give return values back to the client directly so that the ALE monitoring is the only channel for feedback.
Error handling:
Another problem with asynchronous communication is error handling. If an error occurs on the server the calling process on the client may have finished already. So the server can not return the error message to the client. A special error handling process required. This process is one of the ALE services. It uses workflow functionality to identify the error and to start the required error handling.
7. Synchronous vs. asynchronous links?
When distributed applications are linked by ALE business processes, the question often arises as to how tight the link should be. Synchronous and asynchronous links have both advantages and disadvantages.
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link. Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client can not be finished (otherwise there would be data inconsistencies).
(Example: There is a logistics system and a financial system. Every stock movement in logistics has to be posted in the general ledger of the financial system. If the link between logistics and finance is synchronous, no stock movement can be recorded in the logistics system if the communication line to the financial system is down.)
Because of this, synchronous links are usually used if the client only wants to get some data from the server and the sub-processes on the server do not have to write any data to the database.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later. The disadvantage of asynchronous links is that the sub-process on the server can not return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
Asynchronous links are used if a synchronous link is not applicable. For the problems with sending return information to the client and with error handling there is some support from the ALE services.
8. Which kind of interfaces do ALE business processes use?
ALE business processes are integrated processes across distributed systems, requiring interfaces between the systems. These interfaces have to be stable to enable the communication between different releases and to reduce the impact of release changes within the distributed environment.
In SAP R/3 release 3.0 and 3.1 ALE uses IDocs as interfaces. An IDocs is a data container for transferring messages asynchronously. They are release independent. Since SAP Release 3.1G BAPIs are a new type of object oriented, stable interfaces that can be called synchronously or asynchronously. Asynchronous BAPIs use IDocs as data containers. ALE business processes can use BAPIs as well. In the future new ALE business processes will use BAPIs as interfaces. But the existing IDocs will still be supported. In time, BAPIs will be created with similar functionality to existing IDoc interfaces.
9. Why does SAP uses ALE instead of database replication or distributed databases?
Database replication is another possibility for doing business object synchronization. However, there are some major disadvantages with database replication. At the moment database replication is database dependent and release dependent within one database. This makes database replication impossible for the use with non-SAP systems and even for the replication between SAP Systems you have to make sure that all systems are running on the same SAP release and the same database release of a single database vendor. Furthermore, with database replication you cannot do things like field conversions or version changes. ALE does not have these shortcomings because it offers application driven data replication independent of the underlying database.
Another technology, distributed databases, is no alternative for ALE at the moment, either. There are some good results of distributed databases available, but the performance is far from sufficient for using it with larger applications like SAP.
10. What is the relationship between ALE and middleware?
For distributed business processes many different services are required. Most of these services are offered by SAP. For some of these services you can also use products that are provided by SAP's complementary software partners or by other companies:
The communication service for doing the pure communication is usually done via Remote Function Call (RFC). RFC is provided by SAP for most platforms both for synchronous and asynchronous communication. There are other messaging systems for the communication service available as well, like IBM's MQSeries. However, the communication between SAP and the messaging system is still done via RFC.
For the serialization of asynchronous communication the RFC provides little functionality at the moment. The serialization has to be checked by the application. ALE offers some support to do these checks. The serialization of the RFC communication will be improved in the future. Serialization services are provided by some of the existing messaging systems, but even they can not guaranty a 100% serialization of the communication, since they use RFC for the connection to SAP.
The monitoring and error handling of the communication is done via services provided by the RFC and ALE. If messaging systems are used for the communication they also offer some monitoring and error handling functionality.
If a non-SAP system is involved in the ALE business scenario and this system does not understand SAP's BAPI or IDoc interfaces, the data has to be mapped to any interface structure that this system offers. For this mapping SAP does not provide a service but it certifies mapping tools from software partners. These tools are called ALE translator. The most known product in this area is probably Mercator from TSI International Software. The same kind of mapping can also be done by 'EDI converters'.
Another type of middleware products offer process ware. This is mainly a combination of the communication service, the mapping service and a set of rules for the mapping. Some ALE translator can be used for this as well.
Receiver determination is one of the ALE services (see above). Parts of this service can also be provided by some of the messaging systems, but you cannot use these systems without using ALE receiver determination.
For the other ALE services like application monitoring, application error handling, semantic synchronization and business process harmonization, there are no middleware products available as a replacement of ALE.
ALE is open for the use of middleware products for the distribution, but in most cases the additional middleware is not necessary. In a communication between different SAP systems usually the use of additional middleware makes no sense at all. For the communication between SAP and non-SAP systems there might be some benefits, especially if the middleware is used at the company already. The only middleware tool that is really required if the non-SAP system does not understand BAPIs or IDocs is an ALE translator.
Check different sites for more information.
Regards

MPS and MRP question

Hi all,
There are two kinds of planning run (i.e. MPS and MRP). I have few questions on this.
1 - Do I need to setup two background jobs, one for MPS job, and another follow by MRP job, in the system?
2 - Can I just run MPS using MD40 (total MPS run) without perform MRP run (i.e. using any of the MD02)?
3 - Does MPS ONLY plan one level only? in another word, all the second level onward will require another separate MRP run to show all the subsequent level dependent requirement?
4 - if there is one FG, and it has 2nd level of semi-FG bom compenent, the semi-FG has another level of semi-FG and subseuqently Raw material level. In this kind of scenario with many level, it is good practise and it SHOULD use MPS to first plan for the first level FG? and later subsquent level use MRP to plan? Am I correct?
thanks.
tuffy

Hi,
No,
You can MD40 and then MD02
Usually Only those materials which affect companies profit will be taken for MPS, hence few materials will be available for A importance, so you run level by level for MPS, rest will run under MD02, it depends on the business process.
When running MRP using transaction MD02 and MD41, what the difference should be?
There is no difference in the processing logic as such. The only difference is that MPS only acts on materials with an MRP type relevant to MPS (e.g. M0, M1, etc...), and MRP acts on materials with an MRP type relevant to MRP (e.g. PD). How the materials are processed is exactly the same.
This functionality allows you to run MRP for 2 sets of materials separately (and with a different frequency).
For example, some businesses may do planning for their finished goods once per week, but would want to run MRP for their
components daily (although this is generally not necessary with SAP). So, for this example, you would define all finished goods with an MRP type relevant for MPS, and all components with an MRP relevant.
Basically, MPS is a form of MRP that concentrates planning on parts or products that greatly influence the company profits or those that require critical resources. Items marked as master schedule items can be finished goods, assemblies or raw materials. These items are selected for separate MPS run that takes place before the MRP planning run. MPS run is executed without any BOM explosion. This is to allow the MRP controller to ensure that the master schedule items are correctly planned before any detailed MRP run take place.
As you can see, there are not too differences if you review MRP and MPS isolated, but lets think the BIG PICTURE, and can find the difference is just an procedure stuff:
1: RUN MPS (tcode: MD40). SAP do the planning run multilevel, also considering the MRP materials.
2: Do the the necesary MANUAL changes in your MPS materials Planned Orders, remember that the planning run is "JUST AN ADVICE" and never can replace the human decision. Here, you have your MPS Plan, and also the consumtion Plan (dependant requirements)
3: Then, with the dependant requirements OK (acording to MPS's Materials Planned Orders), do MRP RUN (tcode: MD01). The MRP run dont change the MPS plan.
The idea of MPS and MRP is to "separate" materials, in order you can run "masive process" in order. The algorith of mps and mrp are the same. Both work with the PlanTime Fences and Fixation types, rescheduling is the same, and so on.

Testing MRP scope of planning and MRP lists

Hi,
I am configuring the scope of planning and want to know how can I test if the planning is happening in the sequence as specified in the scope of planning. I would have around 20 plants in the scope. I thought of going after the time stamp on the receipts created by the system. Is there any table like MDKP which can show me the sequence of planning ?
Also what is the use oif the tcode MD08.... delete MRP lists ? what is the use of deleting these lists besides keeping the system clean
Thanks

Hi
Reorganization of the MRP Lists - MD08
A report is available for reorganizing the MRP lists which you can find in the menu for MRP under the menu option, Environment. If you enter the selection criteria, plant, material, and MRP date, the system deletes all the MRP lists from the database that are no longer required.This report can also be started in a test session and you can instruct the system to print out a list of all the deleted MRP lists.
Further
Deleting MRP Lists - Manually in MD05
If the MRP list is no longer required, you can delete it manually. In order to do this, choose MRP list ® Delete document. The MRP list will be deleted.If you do not delete the MRP list manually, it is stored in the system until a new MRP list is created by a further planning run.
regrads
muthuraman.d

Item category and mrp type combination not allowed in MTO

Hi,
i am working on make to order without variant configuration scenario,
while creating any customer order i am getting following error.
"This combination of item category YBTA(customized item category) and MRP type (i have used mrp type PD ) for material is not allowed.", due to this error i am not able to create any order.
Please help me to solve this problem.
Regards
Edited by: abhijeet rachkuntwar on Aug 24, 2009 7:47 AM

I have the same problem. You have posted the question long time back. if you happen to solve the problem plz help me by answering your question. if not, I would appreciate help from all the experts here
Many ThanX.

Forecast and MRP type

Hi,
I am in the process of designing a system where there is one DC which gets all sales orders and one mfg plant whihc manufactures and then STOs the material to the DC. Would it be a good thing to have the same forecast for the same material in the same preiods in the DC and the mfg plant, with the sales orders consuming the DC forecast and the STO consumng the mfg plant forecast ? I cannot think of any other way for the DC to drive the demand to the mfg plant and the mfg plant working with this demand to begin manufacturing and component sourcing.
Also I ran a forecast with the MRP type PD. I was expecting VV to be the only MRP type which will allow forecast to be run but looks like PD allows forecast as well. Is that corrrect ?
Thanks

Hello GS
It is not necessary to define the forecast on both plants, only on the plant where the sales orders will be received. Then, on the material master, you define a special procurement type such as "production in alternative plant" or "stock transfer" and MRp will automatically redirect the requirements from the DC to the manufacturing plant.
Take a look on the following link for more details:
Multi-Plant/Site Planning - Material Requirements Planning (PP-MRP) - SAP Library
Yes, PD allows the forecast. If you want to know which MRP types allow the forecast, take a look on the MRP type customizing transaction OMDQ. There is a setting where you define if the forecast is optional, mandatory or not allowed for the MRP type.
BR
Caetano

MPS and MRP

Hi experts,
Is there any difference between planning done using (a) MD41 (for a material of MRP type M0)
and
(b) planning done using MD02 for the same material with MRP type PD?
If I am going to do a MPS for a material of MRP type M0 using MD41, it doesn't make any difference whether I do a separate MRP (say MD02) for its components which are of MRP type PD, am I right?
Thank you very much for your time.

Hi Sethuraman,
This will be relevant for firming. Yes.You are correct regarding the firming part. But there is a difference between MRP and MPS. These are applicable for MD41 and MD02.
Difference between MPS and MRP
Technical difference between MRP and MPS
Regards,
Krishnendu.

Bill material in SD and MRP

Similar Messages

Maybe you are looking for