MRP Logic

Hi All
Does anybody know without using "Hard Pegging" if the logic normally used in MRP can be altered in Oracle. As standard where you already have an open purchase order for an item and you place demand in front of the scheduled due date of the PO MRP recommends you reschedule that PO in before planning any new supply.
What I am after checking is, whether where appropriate any new planned supply could be done before any rescheduling of an item.
Thanks
Keith

MRP do not suggest rescheduling for Firmed orders.
I don't know how it works with Purchase order.
But for discrete job : if the discrete job is not firmed, MRP suggest to reschedule it to match the demand. If the discrete job is firmed , MRP does not suggest to reschedule it. It suggest to create a new work order.

Similar Messages

MRP Logic -Negative Available quantity in MD04

Hi Experts,
We have negative available quantity in MD04. There are no receipts generated particularly for some period even after MRP Run.
MRP Type is maintained as P1- MRP Fixing type.
Safety time is maintained as 3 days.
Planning strategy is 40.
Please suggest, what would be the reason, why i am not getting schedule lines between 09-Aug and 27-Aug which makes available quantity minus, after that there are generation of schedule lines.
Please help with inputs..

Hi,
MRP type P1 is used with planning time fence(mandatory).
Have you used pl time fence. How many days? For those period system will not generate any more planned order.
Regards,
Dharma

FG Actually dates requirement

Dear All,
I am facing one problem, first for your information i have maintained the following inputs in material master.
For Finished Good (FERT)
in-house production time = 5 days
For dependent component
Planned delivery time = 5 days
Now suppose if we feed the order in md01 on 16.12.2011, then the order report after MRP run in md04 generated shows dependent materials requirement date as 11.12.2011 , but i don't want requirement date to be display i want component delievery date as per material master which should be on 22.11.2011 as i have feed the order today. if this is possible then what i will do i will release the planned order to production order and will make FG ready till 27.11.2011
This way i will serviced the FG before the final deadline of 16.12.2011
Please provide me a good solution

Phalgun,
It is not clear what your expectation is.
You say that for Finished goods, you have a planned order. The finish date is Dec 16.
You say that for Component part, you have a dependent requirement (from the FG planned order) of Dec 11.
If you run MRP against the component part (will assume the component part does not use consumption MRP logic, and assume the component part is externally procured), you will get a purchase req which has a completion date of December 11 and a release date of Dec 6. These are the dates you must meet in order to finish the FG planned order on Dec 16.
Now you mention another date: Nov 22. I don't know what this represents. However, if you have created a purchase req for the component, which has a finish date of Nov 22, and you wish to start the FG order early, e.g. on Nov 22, then just change the planned order for the FGs accordingly (earlier date). Alternatively, you can just change the date when you convert the planned order to a production order.
Or, if I have misunderstood your question, please explain in greater detail.
Best Regards,
DB49

Use of Pegging requirements

Hi all,
Please explain the use of without pegging button in MD04
(When we put cursor on production order and press the pegged requirements button, we can see the pegged requirements buttons for some materials). It doesn't come for all materials.
Please explain its functionality.
Regards,
Ravindra

Pegging
Use
If you implement the component Grouping, Pegging, Distribution for project-based production procedures, you can use pegging to determine the proportional assignments of replenishment elements (production orders, purchase orders) for a grouping WBS element to the objects causing the requirements (reservations, planned independent requirements). These assignments form the basis for the cost distribution that follows and that distributes the costs for the procurement elements of grouped requirements to the original projects.
Pegging can be performed in two different ways:
When you make assignments according to MRP Logic, the assignment of replenishment elements to pegged requirements takes place according to the current requirements planning situation. Previous assignments are not taken into account.
The second option is the use of the Fixing Rule: during the assignment process, the attempt is made to copy as many assignments for a replenishment element as possible form the previous pegged requirements run. This means that cost transfer postings at a later date can be avoided.
Special rules must be applied for the assignment of exceptions (surplus, scrap and stock differences).
The transactions for pegging and cost distribution are not in the SAP menu. The function can only be released after agreement with SAP. Due to the complexity of the grouping, pegging and distribution (GPD) process, you should discuss your relevant business processes with a consultant from the SAP Industry Unit Aerospace and Defense.
Prerequisites
To execute pegging, the following prerequisites must be met:
Grouped material requirements under one or several grouping WBS elements must exist for the WBS elements
You have assigned a distribution profile to your grouping WBS element in Customizing
You have assigned a logic for the execution of pegging on plant level in Customizing under Pegging: General Settings.
You have assigned rules for the assignment of exceptions in Customizing under Pegging: General Settings.
You have maintained the movement types that are allowed for pegging in Customizing.
You can find further information on the necessary Customizing activities in the SAP IMG under Logistics ® Project System ® Costs ® Automatic and Periodic Allocations ® Pegging and Distribution.
If you want to use a cost structure that deviates form the production structure, you have created break points.
You have created special WBS elements for the assignment of exceptions (scrap. surplus and stock differences) either on plant level or grouping WBS element level. You can find further information under Assigning Exceptions.
You have assigned grouping WBS elements of category 1 (valid for all materials) to a plant. You can find further information under Assigning Grouping WBS Elements to a Plant.
You have executed material requirements planning (MRP). You can find further information under Starting a Multi-Level Single-Item Planning Run.
Features
Pegging contains the following functions:
Determination of the pegged requirements assignments
Determination of break points
Assignment of exceptions (scrap, surplus, stock differences)
Processing assignments
Transfer posting material to material
Reporting
The following functions are not supported in pegging:
cross-plant processes
use of serialized materials
use of manufacturer part numbers or supersession materials
assignment of requirements form sales orders to projects

Question : Whether Serial number can be used in REM

Hi ,
Can you please give me more documents related to REM and is it possible to use Serial number
profile / serial number in REM.
Regards,
Balaji

Hi,
Yes we can use the serial numeber in REM also
that is all depends on your scenario.
The scenario Repetitive Manufacturing is typically used where the products are being produced in repetitive environment with rate or quantity based planning and scheduling. Planning is often production line oriented. Material supply and production confirmation is is line and quantity based and typically less order oriented.
You use this process to create a production plan in repetitive manufacturing. The system creates one or more planned orders that have a direct reference to a sales order item on the basis of which the material is produced. The process includes analysis, planning according to MRP logic and evaluation of the planning results. You use this process to create a production plan in repetitive manufacturing. Repetitive manufacturing can be used for make-to-stock production. The process includes analysis, planning according to MRP logic and evaluation of the planning results
Go through below link for PDF.
[http://help.sap.com/printdocu/core/print46c/en/data/pdf/PPREM/PPREM.pdf]
Regards,
Nilesh
Edited by: nilesh ithape on Mar 26, 2009 6:28 AM

MRP Area tables for MD06 information access like SQ01, DBM logical database

We currently use SQ01 DBM logical database to access MD06 information (tables MDKP and MDTB). The MRP results from the MRP Area are not showing in this query. This implies that the MRP area, MRP results are stored in other tables.
I have reviewed tables (MDLV, MDMA, MDLG, DVER, MDIP) from a similiar thread. However, they do not contain the MRP data (planned orders, stock, production orders ect) like in the DBM logical database.   This data access is very powerfull for exporting planning data for more robust analysis.
Any help is much appreciated.
Thank you

Hi,
       Please try FM: 'AUFBAUEN_MDPSX_ANZEIGEN'.
    MD06 dame come many table.
Example:
(Plant level)
icm61w-fabkl = wk_fabkl.                  :Factory calender
imt61d-matnr = p_matnr.                    : Materials
imt61d-werks = it_tbl-werks.            : Plant
AUFBAUEN_MDPSX_ANZEIGEN 呼出
CALL FUNCTION 'AUFBAUEN_MDPSX_ANZEIGEN'
    EXPORTING
      ecm61w      = icm61w
      ecm61x      = icm61x
      emt61d      = imt61d
      et399d      = it399d
      ECM61B      =
      ESFILT      =
    IMPORTING
      icm61m      = wa_e_cm61m
      imdkp       = wa_e_mdkp
      imdsta      = wa_e_mdsta
    TABLES
      mdpsx       = it_mdps
regards,
   Gaito

MRP Types and Logic of Calculating

Hi Experts,
I have a issue regarding MRP Types,ie,one of my client wants to know the detailed instruction of MRP types and each MRP type functions.I have given him an explantion in general of all MRP Types,but now he wants to know the detailed logic for each MRP type, for example which include in calculating and how to do calculating.
Request everybody to provide if you have some detailed SAP instruction for this or not.
Awiting for your replies.
Cheers,
Kumar.S

Dear,
Brahm,Vivek,Prasabh,Dharma,Murali,Brahmji,Radha..and all our experts...
Awaiting 4 ur replies.
pls respond.
Cheers,
Kumar.S

SAP Add Pricing Tier Logic to the MRP Purchase Req Calculation

Hi experts,
ISSUE: SAP Add Pricing Tier Logic to the MRP Purchase Req Calculation .
> MRP currently generates purchase requisitions based strictly on a calculation of inventory, open orders, forecast, and purchase orders. The purchase req quantities do not take advantage of the pricing tiers and their associated quantity discounts. MRP may recommend a PO for 913 units. At no time would a planner ever order such a specific quantity. In addition, the planner would increase the order to 1020 to get the price discount for 1000 units (rounded to 1020 for carton quantity). SAP should include a preset order table which would evaluate the MRP calculation and recommend an appropriate quantity based on the contract pricing tiers.
pls let me know it is posible or need any enhancement and how ?
thanks
humera

Hi,
Rounding profile works for u r query, there u can maintain quantity rounding for purchase process, also the rounding off method will set the limit of rounding for given unit of measure. The rounding off method can be maintained in SPRO > Material Managment>purchasing >order optimizing> Quantity optimizing and allowed logistic unit of measure-->Unit of measure rounding rules.
Hope this will help u.
Rgd
Shekhar

Creation of SDEB's for MRP type = VB materials.

Hi Gurus,
When we run plant wise MRP, SDEB's are created instead of Purchase requisitions for all Manual re-order point materials. We understand that SDEB's are created when the stock of tha material is above tha Re-order point, and this SDEB's indicate tha MRP controller whether he can create manually Purchase requisitions or not.
But, we are getting these SDEB's for the materials that have stock below the Re-order point as well. Which is not correct i think.?
For your information, when we run material wise MRP there are no SDEB's at all.
Please explain what might be the Root cause and the solution to over come this..
Thanks for your understanding..
Naveen.A

Dear colleague,
without checking the issue it is difficult to know if there is an error.
Please check if the following information can explain the behaviour of your system:
A)When you do MD01 or MDBT the creaton indicators defines in the
customising are used . whereas when you run MD02 or MD03 the creation
indicator on the individual screen is used.
Single-item planning and total planning follow a different logic
concernng the creation indicators.This is also described in the
documentation for Master Planning/Materials Planning (Chapter 4, Section
2) and in the Implementation Guide.
Single-item planning:
        The entered creation indicators are generally valid.
Total planning:
       The entered creation indicators are used as default values.
       For materials from an MRP group, the values from the MRP group
       apply (if available).
       The creation indicator for delivery schedules can additionally be
       specified per plant. This is used if nothing was specified via
       the MRP group.
       Thus, the priority is as follows:
      1. MRP group
      2. Plant
      3. Initial screen
B)In MD02 system can de multilevel (For components of a header Materia)
or/and Multiplant (Stock Transfre ) planning. In such cases for all the
materials involved the creation indicator used in the screen is used.
C)The creation indicator makes sense only for materials having
procurement type external procurement (F) in material master. For the
materilas which are produced in house (Procurement type E) system will
always create planned orders.
    And Materials having procurement type X(Both procurement types ) is
treated as Inhouse produced material by planning . Thus for such
materials system will always create a planned order. Now this planned
order can be converted into a production orer or into a purchase
order(via purchase Requisition).
    When you run MRP with "Create Purchase Requisition " in the opening
period , then the syetm uses in the opening period defined via the
scheduling margin Key. In material master , MRP 2 View we maintain
scheduling margin key. And in Transaction OPP1->Planning->Scheduling and
Capacity Parameters ->Define floats we maintain the opening periods per
plant. I am attaching details of Opening period :
   opening period: Opening period is the time which the MRP controller
needs to analyse.Thus he has this buffer with him to rectify any issues
before converting the planned order into purchase requisition.
The opening period is only used in backward scheduling.
Suppose There is a requirement for a material on date =RD1
Let the Goods receipt processing time is= T1
Let the planned delivery time =L1
Let the purchasing Processing time = X1
Let the opening period for this material is P1
Time line for external procurement:
        Planned Del   Pur proc         GR Process
          Time            Time          Time
___|__________|_________|___________|___
              L1            X1         T1
   SD                                         RD1
Now accoring to Basic scheduling:
   Receipt/Requirements Date(RD1)
   Release/Start Date(SD) = RD1-T1-L1-X1
Now let me explain to you when the planned order an purchase
Requisitions are created:
Let us say the date on which you do MRP be MR1
OD = Opening Date
From above diagram :
                                 Opening Per
                                 In Sch Mar Key
__________________|______________|
XX                          OD                 SD
                                              Release/Start Date
If your MRP date(generally Today) is lying between XX and OD (and
excludind OD)then
MRP creates planned order and if it lies between (and indclind OD)
OD and SD then we create purchase req.
when your MRP date comes between the period OD and SD then you do not
have time left to analyse and therefore instead of you in such cases
forgetting and delaying system automatically creates purchase req.
      In general if , if your order start date or release date is after
the opening period from today then MRP will create planned order.
Oterwise it creates Purchase req.
Check also if you have the note 1063969 applied in your system.
I hope it solves the issue. Otheriwse I think you should open an OSS message with connection to your system,
best regards,
maria

Logical database in sd

hi experts,
i need standard LDB's related to the tables of sd, mm and fi... can anyone help regarding this.....

Ok so here you are, If you want to edit one go to SE36
LDB name
Logical database short text
50V
Delivery in process
AAV
Logical Database RV: Sales Documents
ABCLAIMLDB
Agency Business: Complaints Processing
ABS
ABAP Book: Customer and bookings
ACAC_ACE_LDBDS
Accrual Object Distribution Server Reporting Table
ACAC_ACE_LDBPS
Accrual Engine Posting Server Reporting Database
ACE_FILA_LDBDS
Accrual Object Distribution Server Reporting Table
ACE_FILA_LDBPS
Accrual Engine Posting Server Reporting Database
ACE_SOP_LDBDS
Stock Option Accounting Distribution Server LDB
ACE_SOP_LDBPS
Provisions for Awards: Posting Server LDB
ACEDS_003
Accrual Object Distribution Server Reporting Table
ACEPS_003
Accrual Engine Posting Server Reporting Database
ADA
Assets Database
AFI
Logical database for orders
AGENCYLDB
Agency Business: Logical Database
AKV
Logical Database RV: Sales Documents
ALV
Archiving Deliveries
ARV
Logical Database RV: Sales Documents
ASV
Request Screen for Summary Information
AUK
Settlement documents
AUW
Allocation Table
B1L
Transfer requirements by number
BAF
BAV-Data collector
BAM
Purchase Requisitions (General)
BANK
Logical Database for Table BNKA
BBM
Archiving of Purchase Requisitions
BC405_DIFF_NODES
Example of Different Node Types
BJF
Loans flow records with date restriction(YR
BKK
Base Planning Object
BKM
Purchase Requisitions per Account Assignment
BMM
Documents for Number
BPF
Treasury Business Partner
BRF
Document Database
BRM
Accounting Documents
BTF
Loan portfolios and flows
BTM
Process Order; Print
BUCHUNGSJOURNAL
LDB for Posting Journal
BUD
LDB For Loans Master Data, Conditions, Documents
C1F
Cash Budget Management
CCLDB_AENR
ECH: Change number with status information
CDC
Document structure
CEC
Equipment BOM
CEK
Cost Centers - Line Items
CFK
Data pool for SAP EIS
CIK
Cost Centers - Actual Data
CKA
Costing
CKC
Sales order BOM
CKM
Material master
CKQ
Material Selection for New Costing Solution
CKS
MiniApp. for the Calculator: Sales Order Data
CKS_WAO
MiniApp: Sales Order Items to be Processed
CKW
Costing run: Material Selection
CMC
Material BOM
CPK
Cost Centers - Plan Data
CRC
Work Centers
CRK
Cost Centers - Total
CRZ
Logical database for courses BC220/BC230
CSC
Standard BOM
CSR
Logical database for archiving BOMs
CTC
Functional location BOM
DBM
MRP Documents
DDF
CUSTOMER DATABASE
DPM
Planned Orders
DSF
Loan Debit Position
DVS
Logical database for archiving DMS data
DWF
Loan resubmission
EBM
Purchasing Activities per Requirement Tracking No.
ECM
Purchasing Documents per Material Class
EHS_OH001
Logical Database for Occupational Health
EKM
Purchasing Documents per Account Assignment
ELM
Purchasing Documents per Vendor
EMM
Purchasing Documents for Material
ENM
Purchasing Documents per Document Number
EQI
Logical Database (Equipment)
ERM
Archiving of Purchasing Documents
ESM
Purchasing Documents per Collective Number
EWM
Purchasing Documents per Supplying Plant
F1S
BC: Planned flights, flights and bookings
FDF
Cash management and forecast
FDK
IS-U/FERC: Drill down to line items and paths
FEF
Cash Management - Memo Records
FILA
Lease Accounting
FMF
Funds Management
FPMF
LDB, reads FPAYH and FPAYP
FRF
Drill-down Selection Screen
FSF
Cash Management Totals Records
FTI_BW_CFM_VALUES
Market Values and Simulated Values in Pos. Mgmt
FTI_LO_PERIODS
Loan/CML Period Evaluations
FTI_LO_POSITIONS
Loan /CML Positions
FTI_SWAP_POSITION
Swap Positions
FTI_TR_CASH_FLOWS
Treasury Payment Information
FTI_TR_PERIODS
Treasury: Period-Based Evaluations
FTI_TR_PL_CF
Treasury: Revenue and Cash Flow Reporting
FTI_TR_POSITIONS
Treasury Positions
FTLM_DB01
Limit Management
FUK
IS-U/FERC: Drill back from document line items
G1S
text
GLG
FI-SL Totals and Line Items
GLU3
Flexible G/L
I1L
Inventory data for storage bin
I2L
Warehouse quants for storage bin
I3L
Inventory documents
IBF
Real Estate Logical Database (Lease-Out)
IDF
Real Estate Logical Database
IDFPLUS
Real Estate Plus Logical Database
IFM
Purchasing Info Records: General
ILM
Archiving Purchasing Info Records
IMA
Logical database for investment programs
IMC
IM Summarization (not usable operationally)
IMM
Inventory documents for material
IMR
Approp. requests (not operationally functional)
IMT
Approp. requests (not operationally functional)
INM
Inventory documents
IOC
Shop floor control - order info system
IPM_ACE_LDBDS
Accrual Object Distribution Server Reporting Table
IPM_ACE_LDBPS
Accrual Engine Posting Server Reporting Database
IRM
Reorganization of inventory documents
J5F
Logical Database for new Nota Fiscal Database
K1V
Generating Conditions
KDF
Vendor Database
KIV
Customer Material Information
KKF
Balance Audit Trail of Open Items
KLF
Historical Balance Audit Trail
KMV
SD Documents for Credit Limit
KOV
Selection of Condition Records
L1L
Evaluation Whse Documents
L1M
Stock movements for material
LMM
Stock Movements for Material
LNM
Stock movements
LO_CHANGE_MNMT
Logical database for engineering change management
MAF
Dataset for Dunning Notices
MDF
Logical Database for Master Data Selection
MEPOLDB
Logical Database/Selection of Purch. Order Tables
MIV
BC: Planned flights, flights and bookings
MMIMRKPFRESB
Selection from Reservations
MRM
Reorganization of material documents
MSM
Material master
NOTIF
LDB for Basic Notifications
NOTIFICATIONS
NTI
Logical database object networking
ODC
Shop floor control - orders per MRP controller
ODK
Orders
OFC
Shop floor control - orders per prod.scheduler
OHC
Shop floor control - orders by numbers
OPC
Shop floor control - orders by material
PAK
CO-PA Segment Level and Line Items
PAP
Applicant master data
PCH
Personnel Planning
PGQ
QM: Specs and Results of the Quality Inspection
PMI
Structure database (plant maintenance)
PNI
PM Planning Database
PNM
Planning database
PNM_OLD
Planning Database
PNP
HR Master Data
PNPCE
HR Master Data (Incl. Concurrent Employment)
POH
Production orders database - header
PSJ
Project system
PTRVP
Travel Management
PYF
Database for Payment Medium Print Programs
QAM
Inspection Catalogs: Selected Sets
QAQ
Inspection Catalogs: Selected Sets
QCM
Inspection Catalogs: Codes
QCQ
Inspection Catalogs: Codes
QMI
Logical database (PM notifications)
QMQ
Inspection Characteristics
QNQ
Quality Notifications
QTQ
Logical database for inspection methods
QUERYTESTLDB
Test LDB for InfoSet Query
R0L
Archive selection: Transfer orders (MM-WM)
R1L
Archive selection: Transfer requirements (MM-WM)
R2L
Archive Selection: Posting Change Notices (MM-WM)
R3L
Archive selection: Inventory documents (MM-WM)
R4L
Archive selection: Inventory histories (MM-WM)
RBL
Archiving of transfer requests
REAO
Real Estate: Logical Database for Architecture
REBD
Logical Database for Real Estate Objects
REBP
Logical Database via Partner (Real Estate)
RECN
Real Estate: Selection by Contracts
RECONTRACT
RE Logical Database: (General) Contract
RHL
Archiving of inventory history
RIL
Archiving of inventory documents
RKM
Reservations for Account Assignment
RLI
Logical Database Reference Location
RMM
Reservations for material
RNM
Reservations
RTL
Archiving of transfer orders
RUL
Archiving of Posting Change Notices
S1L
Stock by storage bins
S1L_OLD
Stock by Storage Bins
S2L
Warehouse quant for material
S3L
Stocks
SAK
Completely Reversed Allocation Documents
SD_KUSTA
Logical Database for Sales Summary
SD_ORDER
Logical database for inquiries, contracts
SD_SALES_DOCUMENT
Logical database for inquiries, contracts
SDF
G/L Account Database
SMI
Serial Number Management
T1L
Transfer orders by number
T1L_OLD
Transfer Orders by Number
T2L
Transfer orders for material
T3L
Transfer orders for storage type
T4L
Transfer order for TO printing
T5L
Transfer orders for reference number
TAF
Treasury
TIF
Treasury Information System
TPI
Functional Location Logical Database
U1S
User master reorganization: Password changes
U2S
User master reorganization: Password changes
U3S
User master reorganization: Password changes
U4S
User master reorganization: Password changes
UKM_BUPA
SAP Credit Management: Business Partner
V12L
Pricing Report
VAV
Logical Database RV: Sales Documents
VC1
List of Sales Activities
VC2
Generate Address List
VDF
Customer Database with View of Document Index
VFV
Logical Database RV: Billing Documents
VLV
Logical Database For Deliveries
VVAV
Logical Database RV: Sales Documents
VXV
SD: Billing Document - Export
WAF
Securities position plus additional master data
WOI
Maintenance Item
WPI
Maintenance plans
WTF
Securities positions and flows
WTY
WTY LD
WUF
Sec.-Determ.master data for positions
I hope this will delh

Logical Database

Hi,
I have the following issue:
we need to make use of BADI 'MD_PURREQ_CHANGE' here I need to use Logical Database 'DBM' in my implimentation method. Shall we make use of Logical Databse in ABAP Objects? If yes, could you give any ideas please?
Thanks & regards
Sreenivas

Hi,
I tried several times, it seems that is not possible to make use of Logical Database from ABAP Objects.
IS there any ideas?
I am providing some more details:
While I was testing the MRP BADI the MDTB table is not being updated with any data . OSS note 440016 says that there is a customizing setting by which you can still update the MDTB table but this would lead to performance issues (easier to query though).
In standard SAP, MRP data is stored as an aggregated list (table is stored as a data cluster and I need an ABAP extract to get something meaningful from it) in table MDTC for improved performance.
Does any body having an ideas on this?
Thanks & regards
Sreenivas

Open requirement is not taken in considaration after MRP run.

Hello PP Experts,
I am facing issue with network , prod order and stockrequirement list.
I have a network with qty 2.
1 qty is in stock. (MMBE)
for 1 qty prod order is created and the status is "REL PRT CNF DLV PRC GMPS MANC SECT".
The problem is____________________
Prd order has open requirement and prd ord is still open. The problem is that seem that MRP doesn't take in consideration this requirement as an open requirement and in MD04 it can not be seen. the requirements which we can see have no linked to this production order but only linked to planned orders.
Network can be seen in MD04.
Why prd ord is not visible in MD04.
Mukesh Chauhan

Dear
Why prd ord is not visible in MD04.
It is quite logical that SAP system is behavig correctly .You have Network qty of 2 which has a planned order with same qty .Now in MDO4 you have converted that Planned Order partially to Production order having qty 1 and subsequyenetly , you have processed the order with REL , CRTD , GMPS , CNF, DLV.
Now here is the mistak happend that you have could have keep the Order Confirmation stauts as PCNF AND PDLV so that rest of the qty can be converted to same PO and also you can process CNF through CO11N and MIGO-101 for Final DLV.
When an order is confirmaed and delivered , it will not appear in MD04 even its a partial qty .MD04 can show up the order having REL and CRTD .When the order is GMPS , CNF, DLV , TECO it will disaapear from MD04 as per the Filter set up for MD04 screen -SAP0002 in SPRO-PP-MRP-Evalution -Filter -Define Selection Rule .
So what you need to do either you revesre the DLV -MIGO-102 and Confirmation-CO13 and carry out PCNF,PDLV so that rest of the planned oqty can be processed with same order number .Or if you know the Planned Order number , then got CO40 - Individual Conversion -Enter Planned Order -Convert to PO and prcess subsequenetly
Regards
JH

Logic needed Pls help

Hi
I have to add 'Upload excel file' option in Material consumption program. Current logic is Uploading Unix file. Can any one give me some idea pls.
following is my coding
PROGRAM ZMDM0081 MESSAGE-ID ZM.
TABLES: MARA.
* Resource file record structure
DATA: BEGIN OF RECORD,
        MATERIAL_NUMBER(10),
        PLANT(5),
        CORRECTED_VALUE_19(11),
        CORRECTED_VALUE_18(11),
        CORRECTED_VALUE_17(11),
        CORRECTED_VALUE_16(11),
        CORRECTED_VALUE_15(11),
        CORRECTED_VALUE_14(11),
        CORRECTED_VALUE_13(11),
        CORRECTED_VALUE_12(11),
        CORRECTED_VALUE_11(11),
        CORRECTED_VALUE_10(11),
        CORRECTED_VALUE_09(11),
        CORRECTED_VALUE_08(11),
        CORRECTED_VALUE_07(11),
        CORRECTED_VALUE_06(11),
        CORRECTED_VALUE_05(11),
        CORRECTED_VALUE_04(11),
        CORRECTED_VALUE_03(11),
        CORRECTED_VALUE_02(11),
        CORRECTED_VALUE_01(11),
      END OF RECORD.
* Working variables
DATA: RECORD_READ(6)   TYPE P,
      RECORD_INSERT(6) TYPE P,
      RECORD_OMIT(6)   TYPE P,
      MATERIAL_NUMBER LIKE MARA-MATNR,
      G_BRGEW          LIKE MARA-BRGEW,
      N_NTGEW          LIKE MARA-NTGEW,
      PLANT            LIKE MARC-WERKS,
      REMARKS(50),
      FLAG(1),
      RECORD_FLAG(1),
      INTENSIFIED_FLAG(1),
      NUMBER(6)        TYPE P.
* Constant variables
CONSTANTS: VALID   VALUE '1',
           INVALID VALUE '0',
           ON      VALUE '1',
           OFF     VALUE '0'.
* Reporting groups
FIELD-GROUPS HEADER.
* Insert into groups
INSERT MATERIAL_NUMBER
       PLANT
       REMARKS
       INTO HEADER.
* BDC parameters
SELECTION-SCREEN BEGIN OF BLOCK ONE WITH FRAME TITLE TEXT-010.
PARAMETERS: FILE(30) TYPE C
                      DEFAULT '/export/remote/data.txt'
                      LOWER CASE
                      OBLIGATORY,
             SESSION LIKE RL04I-MAPPE
                      OBLIGATORY
                      DEFAULT '8301_MM02',
                      UNAME LIKE SY-UNAME DEFAULT SY-UNAME.
SELECTION-SCREEN END OF BLOCK ONE.
* Data conversion parameters
SELECTION-SCREEN BEGIN OF BLOCK TWO WITH FRAME TITLE TEXT-020.
PARAMETERS MONTH(2) TYPE N DEFAULT 1.
SELECTION-SCREEN END OF BLOCK TWO.
* Notes to user
SELECTION-SCREEN BEGIN OF BLOCK THREE WITH FRAME TITLE TEXT-030.
SELECTION-SCREEN COMMENT /5(70) TEXT-040.
SELECTION-SCREEN COMMENT /5(70) TEXT-050.
SELECTION-SCREEN END OF BLOCK THREE.
MOVE UNAME TO SY-UNAME.
* Including SAP R/3 BDC customized include
INCLUDE ZSIN0001.
* Verifying the path & file name
AT SELECTION-SCREEN ON FILE.
PERFORM RESOURCE_FILE_OPEN.
* Processing BDC
START-OF-SELECTION.
PERFORM SESSION_OPEN.
PERFORM SESSION_GENERATION.
PERFORM SESSION_CLOSE.
CLOSE DATASET FILE.
* Printing execution report
END-OF-SELECTION.
SKIP.
WRITE /15 'BDC & SYSTEM PARAMETERS -' COLOR 3.
SKIP.
WRITE: /15 'Resource path & filename ..........', FILE,
         /15 'Session name ......................', SESSION,
         /15 'ABAP/4 Program name ...............', SY-REPID,
         /15 'Client ............................', SY-MANDT,
         /15 'SAP System ID .....................', SY-SYSID,
         /15 'SAP Release .......................', SY-SAPRL,
         /15 'Host ..............................', SY-HOST,
         /15 'Operating system ..................', SY-OPSYS,
         /15 'Database system ...................', SY-DBSYS,
         /15 'User ID ...........................', SY-UNAME,
         /15 'Date ..............................', SY-DATUM,
         /15 'Time ..............................', SY-UZEIT.
SKIP 3.
WRITE /15 'DATA CONVERSION DEFAULT PARAMETERS -' COLOR 3.
SKIP.
WRITE: /15 'Start at previous month ............', MONTH.
SKIP 3.
WRITE /15 'EXECUTION REPORT -' COLOR 3.
SKIP.
WRITE: /15 'Total records read form file ......', RECORD_READ,
         /15 'Total records insert to BDC .......', RECORD_INSERT,
         /15 'Total records omitted .............', RECORD_OMIT.
NEW-PAGE.
SORT.
LOOP.
    ADD 1 TO NUMBER.
    IF INTENSIFIED_FLAG EQ ON.
      FORMAT COLOR 2 INTENSIFIED ON.
      MOVE OFF TO INTENSIFIED_FLAG.
    ELSE.
      FORMAT COLOR 2 INTENSIFIED OFF.
      MOVE ON TO INTENSIFIED_FLAG.
    ENDIF.
    WRITE: /1 NUMBER, MATERIAL_NUMBER, PLANT, REMARKS.
    POSITION SY-LINSZ.
    WRITE ' '.
ENDLOOP.
* Reading resource file and generating BDC session
FORM SESSION_GENERATION.
DO.
    READ DATASET FILE INTO RECORD.
    IF SY-SUBRC NE 0 OR RECORD IS INITIAL.
      EXIT.
    ENDIF.
    ADD 1 TO RECORD_READ.
    PERFORM RECORD_CONDENSATION.
    PERFORM RECORD_VERIFICATION.
    CHECK RECORD_FLAG EQ VALID.
    REFRESH BDCDATA.
    PERFORM SCREEN_SEQUENCE.
    PERFORM BDC_TRANSACTION USING 'MM02'.
    IF SY-SUBRC EQ 0 .
      ADD 1 TO RECORD_INSERT.
    ELSE.
      ADD 1 TO RECORD_OMIT.
    ENDIF.
ENDDO.
ENDFORM.                    "SESSION_GENERATION
* Condensing the record fields
FORM RECORD_CONDENSATION.
CONDENSE: RECORD-MATERIAL_NUMBER,
            RECORD-PLANT,
            RECORD-CORRECTED_VALUE_19,
            RECORD-CORRECTED_VALUE_18,
            RECORD-CORRECTED_VALUE_17,
            RECORD-CORRECTED_VALUE_16,
            RECORD-CORRECTED_VALUE_15,
            RECORD-CORRECTED_VALUE_14,
            RECORD-CORRECTED_VALUE_13,
            RECORD-CORRECTED_VALUE_12,
            RECORD-CORRECTED_VALUE_11,
            RECORD-CORRECTED_VALUE_10,
            RECORD-CORRECTED_VALUE_09,
            RECORD-CORRECTED_VALUE_08,
            RECORD-CORRECTED_VALUE_07,
            RECORD-CORRECTED_VALUE_06,
            RECORD-CORRECTED_VALUE_05,
            RECORD-CORRECTED_VALUE_04,
            RECORD-CORRECTED_VALUE_03,
            RECORD-CORRECTED_VALUE_02,
            RECORD-CORRECTED_VALUE_01.
ENDFORM.                    "RECORD_CONDENSATION
* Verifying record fields
FORM RECORD_VERIFICATION.
MOVE VALID TO RECORD_FLAG.
UNPACK RECORD-MATERIAL_NUMBER TO MATERIAL_NUMBER.
SELECT SINGLE * FROM MARA
                      WHERE MATNR EQ MATERIAL_NUMBER.
IF SY-SUBRC NE 0.
    ADD 1 TO RECORD_OMIT.
    MOVE: RECORD-PLANT TO PLANT,
          TEXT-060     TO REMARKS,
          INVALID      TO RECORD_FLAG.
    EXTRACT HEADER.
    EXIT.
ELSE.
    IF MARA-NTGEW > MARA-BRGEW.     "add to check for net weight > grow
      MOVE '1' TO FLAG.
    ELSE.
      MOVE ' ' TO FLAG.
    ENDIF.
ENDIF.
MOVE RECORD-PLANT TO PLANT.
SELECT SINGLE MATNR WERKS INTO (PLANT, MATERIAL_NUMBER)
                            FROM ('MARC')
                            WHERE MATNR EQ MATERIAL_NUMBER
                            AND   WERKS EQ PLANT.
IF SY-SUBRC NE 0.
    ADD 1 TO RECORD_OMIT.
    MOVE: TEXT-070 TO REMARKS,
          INVALID TO RECORD_FLAG.
    EXTRACT HEADER.
ENDIF.
ENDFORM.                    "RECORD_VERIFICATION
* Performing the screen sequence
FORM SCREEN_SEQUENCE.
PERFORM SCREEN_SAPLMGMM_0060.
PERFORM SCREEN_SAPLMGMM_0070.
PERFORM SCREEN_SAPLMGMM_3005.
PERFORM SCREEN_SAPLMGMM_0081.
PERFORM SCREEN_SAPLMGMM_3006.
PERFORM SCREEN_SAPLMGMM_3110.
ENDFORM.                    "SCREEN_SEQUENCE
* Change Material: Initial Screen
FORM SCREEN_SAPLMGMM_0060.
PERFORM BDC_DYNPRO USING 'SAPLMGMM'   '0060'.
PERFORM BDC_FIELD USING 'RMMG1-MATNR' RECORD-MATERIAL_NUMBER.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/5'. " Select view(s)
ENDFORM.                    "SCREEN_SAPLMGMM_0060
* Select view(s)
FORM SCREEN_SAPLMGMM_0070.
PERFORM BDC_DYNPRO USING 'SAPLMGMM'            '0070'.
PERFORM BDC_FIELD USING 'MSICHTAUSW-KZSEL(01)' 'X'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'           '/0'. " Enter
ENDFORM.                    "SCREEN_SAPLMGMM_0070
* Change Material: Basic data
FORM SCREEN_SAPLMGMM_3005.
PERFORM BDC_DYNPRO USING 'SAPLMGMM'   '3005'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'SP08'.             " MRP 1
IF FLAG EQ '1'.
    PERFORM BDC_DYNPRO USING 'SAPLMGMM'   '3005'.
    PERFORM BDC_FIELD USING 'BDC_OKCODE'           '/0'.
ENDIF.
ENDFORM.                    "SCREEN_SAPLMGMM_3005
* Organizational levels
FORM SCREEN_SAPLMGMM_0081.
PERFORM BDC_DYNPRO USING 'SAPLMGMM'    '0081'.
PERFORM BDC_FIELD USING 'RMMG1-WERKS' RECORD-PLANT.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '=ENTR'. "Continue
ENDFORM.                    "SCREEN_SAPLMGMM_0081
* Change Material: MRP 1
FORM SCREEN_SAPLMGMM_3006.
PERFORM BDC_DYNPRO USING 'SAPLMGMM'   '3006'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'ZU11'. " Consumption
ENDFORM.                    "SCREEN_SAPLMGMM_3006
* Change Material: Consumption
FORM SCREEN_SAPLMGMM_3110.
CONSTANTS: PREVIOUS_MONTH VALUE 'X',
             THIS_MONTH     VALUE ' '.
DATA: ROW_POSITION(2)      TYPE N VALUE 0,
        WS_POSITION(2)       TYPE C,
        FIELDNAME            LIKE BDCDATA-FNAM,
        CONSUMPTION_QUANTITY LIKE RECORD-CORRECTED_VALUE_01.
PERFORM BDC_DYNPRO USING 'SAPLMGMM' '3110'.
* if month eq previous_month.
*    move 1 to row_position.
* elseif month eq this_month.
*    move 0 to row_position.
* endif.
MOVE MONTH TO ROW_POSITION.
DO 19 TIMES VARYING CONSUMPTION_QUANTITY
              FROM RECORD-CORRECTED_VALUE_01
              NEXT RECORD-CORRECTED_VALUE_02.
    IF ROW_POSITION GT 11.
      MOVE 1 TO ROW_POSITION.
      PERFORM BDC_FIELD USING 'BDC_OKCODE' 'VWNP'. " Page down
      PERFORM BDC_DYNPRO USING 'SAPLMGMM'   '3110'.
    ENDIF.
    UNPACK ROW_POSITION TO WS_POSITION.
    CONCATENATE 'RM03M-VBWRT(' WS_POSITION ')' INTO FIELDNAME.
    IF CONSUMPTION_QUANTITY+0(1) EQ '-'.
      SHIFT CONSUMPTION_QUANTITY LEFT BY 1 PLACES.
      CONCATENATE CONSUMPTION_QUANTITY '-' INTO CONSUMPTION_QUANTITY.
    ENDIF.
    PERFORM BDC_FIELD USING FIELDNAME CONSUMPTION_QUANTITY.
    ADD 1 TO ROW_POSITION.
ENDDO.
PERFORM BDC_DYNPRO USING 'SAPLMGMM' '3110'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/11'. " Save
ENDFORM.                    "SCREEN_SAPLMGMM_3110
Include Program
* BDC data table and record structure defination
DATA BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
* Opening a resource file
FORM RESOURCE_FILE_OPEN.
DATA ERROR_MESSAGE(40).
*Begin of changes Mod01
* OPEN DATASET FILE FOR INPUT IN TEXT MODE MESSAGE ERROR_MESSAGE.
OPEN DATASET FILE FOR INPUT IN TEXT MODE ENCODING DEFAULT MESSAGE
                                                      ERROR_MESSAGE.
*End of changes Mod01
IF SY-SUBRC NE 0.
    MESSAGE E000 WITH FILE ERROR_MESSAGE.
ENDIF.
ENDFORM.
* Opening of BDC session
FORM SESSION_OPEN.
CALL FUNCTION 'BDC_OPEN_GROUP'
       EXPORTING CLIENT              = SY-MANDT
                  DEST                = SY-HOST
                  GROUP               = SESSION
                  USER                = SY-UNAME
                  KEEP                = 'X'
       EXCEPTIONS CLIENT_INVALID      = 01
                  DESTINATION_INVALID = 02
                  GROUP_INVALID       = 03
                  HOLDDATE_INVALID    = 04
                  INTERNAL_ERROR      = 05
                  QUEUE_ERROR         = 06
                  RUNNING             = 07
                  USER_INVALID        = 08.
CASE SY-SUBRC.
    WHEN 01. MESSAGE E001 WITH SY-MANDT.
    WHEN 02. MESSAGE E002.
    WHEN 03. MESSAGE E003.
    WHEN 04. MESSAGE E004.
    WHEN 05. MESSAGE E005.
    WHEN 06. MESSAGE E006.
    WHEN 07. MESSAGE E007.
    WHEN 08. MESSAGE E007.
ENDCASE.
ENDFORM.
* Closing BDC session
FORM SESSION_CLOSE.
CALL FUNCTION 'BDC_CLOSE_GROUP'
    EXCEPTIONS NOT_OPEN    = 01
               QUEUE_ERROR = 02.
CASE SY-SUBRC.
    WHEN 01. MESSAGE E009.
    WHEN 02. MESSAGE E010.
ENDCASE.
ENDFORM.
* Inserting data into BDC
FORM BDC_TRANSACTION USING TRANSACTION_CODE.
CALL FUNCTION 'BDC_INSERT'
       EXPORTING TCODE          = TRANSACTION_CODE
       TABLES     DYNPROTAB      = BDCDATA
       EXCEPTIONS INTERNAL_ERROR = 1
                  NOT_OPEN       = 2
                  QUEUE_ERROR    = 3
                  TCODE_INVALID = 4
                  OTHERS         = 5.
ENDFORM.
* Insert program name & screen number
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
MOVE: PROGRAM TO BDCDATA-PROGRAM,
        DYNPRO TO BDCDATA-DYNPRO,
        'X'     TO BDCDATA-DYNBEGIN.
APPEND BDCDATA.
ENDFORM.
* Inserting field name/BDC_OKCODE/BDC_CUESOR and value
FORM BDC_FIELD USING FNAM FVAL.
CLEAR BDCDATA.
MOVE: FNAM TO BDCDATA-FNAM,
        FVAL TO BDCDATA-FVAL.
APPEND BDCDATA.
ENDFORM.

i have changed the selection screen as follows
SELECTION-SCREEN BEGIN OF BLOCK one WITH FRAME TITLE text-010.
*                                                          "1)
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS p_unix RADIOBUTTON GROUP rad1 .                 "
SELECTION-SCREEN COMMENT 5(26) text-008.
SELECTION-SCREEN POSITION 33.                              "
PARAMETERS: file(128) TYPE c
                      DEFAULT '/export/remote/data.txt' LOWER CASE.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS p_xls RADIOBUTTON GROUP rad1 .                 "excel file
SELECTION-SCREEN COMMENT 5(26) text-009.
SELECTION-SCREEN POSITION 33.                              "
PARAMETERS: filf(128).
SELECTION-SCREEN END OF LINE.
*>>
*PARAMETERS: file(128) TYPE c
*                      DEFAULT '/export/remote/data.txt' LOWER CASE OBLIGATORY,
PARAMETERS: session LIKE rl04i-mappe OBLIGATORY
                      DEFAULT '8301_MM02',
             uname LIKE sy-uname DEFAULT sy-uname.
SELECTION-SCREEN END OF BLOCK one.
* Data conversion parameters
SELECTION-SCREEN BEGIN OF BLOCK two WITH FRAME TITLE text-020.
PARAMETERS month(2) TYPE n DEFAULT 1.
SELECTION-SCREEN END OF BLOCK two.
* Notes to user
SELECTION-SCREEN BEGIN OF BLOCK three WITH FRAME TITLE text-030.
SELECTION-SCREEN COMMENT /5(70) text-040.
SELECTION-SCREEN COMMENT /5(70) text-050.
SELECTION-SCREEN END OF BLOCK three.

MRP keeps pushing delivery schedules out, refusing to firm them (ME33L)

I hope someone has seen something like this before and can let us know where to look. MRP keeps pushing our delivery schedules out even though it is recommending that they be rescheduled in. What we'd like to happen is for MRP to leave these schedules alone so that they would move inside the time fence and be firmed automatically. Here is what is happening:
Part X, MRP type P1, firming type 1, MRP group blank. Planning time fence 05/07/2007, available quantity -20.
Three schedule lines exist for 05/07/2007, two for 10 and another for 30.
MRP will run tonight. Processing Key = NEUPL, purch req = 2, sched lines = 3, MRP list = 1, planning mode = 2, scheduling = 2
Tomorrow, the planning time fence will be at 05/08/2007 and the three schedule lines will move out to 05/08/2007. The won't move inside the planning time fence and firm up. They SHOULD BE 05/07/2006 and firmed!
We originally thought that we may have to create a release with ME84 before these would firm, but it made no difference. They still won't firm unless someone manually changes the date on each and every schedule line.
Does anyone know what we can change or run to get these schedules to firm up instead of having them pushed out continually?

Hello Randy,
thanks for the update. I didnt remenber this customizing indicator when posting.
Still wondering why planning matters here. I think it should have the same result for all planning modes. Of course planning mode 3 in general should be avoided for performance reasons.
For interested observers I attach the description for this setting in MRP customizing.
Regards, Martin
Indicator: Only Firm Transmitted Schedule Lines
In this step, you can set an indicator which is used to set only those schedule lines that have been transferred to the vendor.
You can firm schedule lines within the planning time fence (in the same way as planned orders or purchase requisitions) according to the master schedule item firming logic. The planning time fence is a number of days that is calculated into the future starting from the current date. Therefore, the last date of the planning time fence changes every day.
In the firming logic, existing schedule lines are also firmed as soon as they move into the planning time fence.
Schedule lines that lie outside the planning time fence and whose quantity is adjusted in the planning run due to a change of the requirements quantity are firmed with the new quantity as soon as the schedule lines move into the planning time fence.
The schedule lines are transferred to the vendor for the amount recorded in the stock/requirements list at the time of the data transfer.
If you only want to firm the schedule lines in the planning time fence that have been checked and transferred to the vendor, you can use the indicator, Only firm transmitted schedule lines. By selecting this indicator, the system only firms the schedule lines that have been sent to the vendor.
For schedule lines whose quantity has changed and which have moved into the planning time fence, the following occurs if this indicator has been set: if the MRP controller/purchaser does not confirm the procurement plan by sending the changed quantities to the vendor, the schedule line quantities that were sent to the vendor in the previous data transfer are firmed within the planning time fence. This guarantees that the system cannot firm any quantities that have not been checked. It also means that the vondor does not receive any messages for unchecked schedule line quantities.
Activities
Define the indicator per MRP group and allocate this MRP group to the materials for which this indicator is to be valid.
Further notes
The message transfer is a purchasing function. You can find it in the purchasing menu, Outline agreement -> Scheduling agreement -> Messages -> Print/transmit.

Link Sales Order and Purchase Order - MRP Pegging - Give Feedback

Oracle Apps Version - 11.5.10.2
Mfg - Discreate manufacturing module along with P2P and OTC..No Projects Module.
Soft Pegging enabled on Items..
Hi Guru,
we have created a SQL to link SO and PO using MRP_Full_Pegging Table,what are issues you see with this logic..would it always give me correct mapping between SO and PO
SELECT
mgr.inventory_item_id Item_ID,
mtl.segment1 Item,
ohll.order_number SO_Number,
--mr.disposition_id,
mr.compile_designator MRP_Plan,
--mipo.line_id,
--poll.line_location_id,
pohll.segment1 P0_Number,
mtl.description Item_Description
FROM
mrp_gross_requirements mgr,
MRP_SCHEDULE_DATES msd,
mtl_sales_orders mso,
oe_order_headers_all ohll,
mrp_recommendations mr,
mrp_item_purchase_orders mipo,
po_line_locations_all poll,
PO_HEADERS_ALL pohll,
mtl_system_items_b mtl
WHERE
msd.mps_transaction_id = mgr.DISPOSITION_ID
and msd.inventory_item_id = mgr.inventory_item_id
and mtl.inventory_item_id = mgr.inventory_item_id
and msd.source_sales_order_Id = mso.sales_order_id
and mso.segment1=ohll.order_number
and msd.organization_id = XXX -- pl use you inv org id
and mr.disposition_id=mipo.transaction_id
And mipo.line_id=poll.po_line_id
and poll.po_header_id = pohll.po_header_id
and mr.inventory_item_id = mtl.inventory_item_id
and mr.compile_designator like '%XXX%' -- pl use MRP plan name
and rownum <100 -- just to limit result set
Order By ohll.order_number desc;
Appreciate your feedback and inputs to make necessary corrections to make it accurate and complete.
thank you.

I tried writing the query to find the supply and demand details in ASCP Planning.
In our scenario we created a sales order '5110416.AT PROJECT.ORDER ENTRY(6.1)' and launch the plan. It has created the plan order and after releasing it has created the internal requisition and then Internal sales order. But the supply sales order number is not populated in order_number column of msc_supplies.
Please help me if I am missing some thing. Just for your info I have run the plan again and then also its not updated. Below is the query which I have written. This is very critical for me. Please advice.
SELECT
MS.ORDER_NUMBER,MS.ORDER_TYPE,MS.ORDER_LINE_NUMBER,MD.SALES_ORDER_LINE_ID,MD.ORDER_NUMBER
FROM
MSC_SUPPLIES MS,
MSC_FULL_PEGGING MFP,
MSC_DEMANDS MD
WHERE 1=1
AND MS.TRANSACTION_ID=MFP.TRANSACTION_ID
AND MD.DEMAND_ID=MFP.DEMAND_ID
AND MD.ORDER_NUMBER='5110416.AT PROJECT.ORDER ENTRY(6.1)'
Thanks in advance.
Regards
RV

MRP Logic

Similar Messages

Maybe you are looking for