Planning Segment Number

Dear SAP Friends,
I am using MDTB,MDKP & MARA table to view the Requierment & receipt qty of material.
Here I get the data as per the MD04 T-code but there is a data which shows with reference of Planning segment number.
Data as per MD04 is shown at Top lines & after that data shows with the reference of Planning segment number which is not shown in MD04.
Could you please explain me what is these data & how it is shown or generate in SAP with what referance?
Please reply.
Thanks & Regards,
Chandra
Edited by: chandra shekhar on Aug 2, 2010 6:06 PM

Chandra,
I wish I could help.  Unfortunately, most ERP systems (as of SAP R/3 4.5) do not update MDTB any more by default.  I do not have access to any system where this table is being actively managed.
Planning segments usually refer to Project segments, or MTO Sales segments.  I would imaging that the contents of the MDTB field PLANR would contain either the Project number or the Sales order item number, formatted.  However, I have no way to validate this assumption.
Rgds,
DB49

Similar Messages

  • Why we should assign Profitability Segment Number in sales Order

    Dear Gurus,
    Can any one tell me why we should assign profitability Segment Number in Sales Order?
    While i am createing the sales order system is asking to assign profitability Segment Number and WBS Element. Even though there is no specific assignment of these fields for incompletion log.
    Can anyone tell me what exactly is the functionality behind this Profitability Segment number?
    Good answers are rewarded with points
    Thanks and Regards
    SAP SD
    Yoganand

    Hi,
    If CO-PA is active settlement transfer the costs and revenue of the sales order item to profitability segment in CO-PA, if not active it gets transferred to G/L account in FI.
    Regarding functionality of Profitability segment - Need to specify Characteristics in CO-PA for profitability segments and these characteristics are used for Information system and planning. Charcteristics which are not involved in profitablity segment remains in the line item of CO-PA. In essence charcteristics decides on profitablity segments.
    Regarding removal of Profitablity segment no in Sales order .Kindly refer back to the earlier threads.
    Thanks & Regards
    Madhu

  • ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$

    A Materalized view is scheduled to update every 12 hours . When it has tried to update it has thrown the error ...
    ORA-12008: error in materialized view refresh path
    ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$"
    too small
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 841
    ORA-06512: at line 1

    Hi,
    Can you increase the size of the UNDO Tablespace ?
    For more information, you can find on this link below:
    http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-01555&objID=c84&dateRange=all&userID=&numResults=15
    Cheers

  • Planned Order Number Ranges

    Hi Gurus,
    I am having two plants defined in one company code.
    Is Planned order number range plant specific?
    My planned order number range in plant-1 is 1000-2000 and it is same in the Plant-2. If I create the planned orders in both plants.
    What is starting number for planned orders in each plant?
    Can I create like this?
    Thanks in advance.
    Regards,
    Jejesh
    Edited by: jejesh yal on Sep 30, 2008 9:25 PM

    Hello,
    If you are creating Planned order using the MRP, you  can set the plant specific Number range for planned Order at OPPQ
    Please check with planned order Number range  tab at OPPQ
    Regards
    Pradeep

  • Planned order number range in apo

    Where planned order number range  can be maintain in apo.
    I am converting agreed plan into planned order but planned order number has generated.
    Please somebody tell me.
    Regards,
    Sunill

    Planned order number ranges can be maintain in
    sproaposupply chain planningppdsglobal settings--maintain number ranges for orders.
    and then you assign the number ranges in
    sproaposupply chain planningppdsglobal settings--maintain global parameters and defaults (in planning tab )

  • Planned order number list

    Hi,
    Can any one tell me in which table system storing planned order number and which numbers getting converted to purchase requisition.
    Your response is apprecited,
    Thanks
    Dipak

    Hi,
           Check the table <b>PLAF</b>.
    Regards

  • Planned order number and Plnkn

    Dear All,
    I need the table link between planned order number and Number of the task list node(PLNKN).
    Thank you in advance
    Regards
    Sailendra.M
    Edited by: nivedita yadav on Jun 25, 2010 2:35 PM

    Dear Nivedita,
    Check with this functional Module in SE37
    BAPI_PLANNEDORDER_GET_DETAIL
    In my understanding I dont think nwe can get this data from table.
    Regards
    S Mangalraj

  • Rollback segment number not shown with name " not shown " too small

    Hi,
    we have a table TABLE1 with a BLOB field FIELD1 on a Oracle 10g database. Today we found out that there is one record in that table that make problems. if we try to read the BLOB data from that record, Oracle shows the error:
    ORA-01555: snapshot too old: rollback segment number  with name "" too small
    The strange thing about it, that the message shows neither the segment number nor the segment's name. Like it has lost the reference to it.
    Could you help please.
    Notes:
    The TABLE1 and the BLOB data are really not big.
    The UNDO tablespace is 2Gb big and just 1% used.
    Thank you very much
    Igor

    Out-of-row LOB undo is maintained in the LOB segment. So the UNDO tablespace and undo retention is not associated with most LOB ORA-1555 issues. Instead the LOB column is created using either PCT_VERSION or RETENTION to manage how much space within blocks or time transpires before the LOB undo is overwritten. In environments with high updates, deletes on rows including LOBs, the chances of ORA-1555 on LOB undo is very high.
    Source:http://blogs.oracle.com/db/entry/troubleshooting_ora_1555
    In the above link you will get plenty of good metalink notes to understand and solve the issue.
    There is no undo segment name in the error message means this error has no relation with undo tablespace/parameter/segment. This might mean that your LOB table is corrupted. Can you drop and recreate/re-populate this table and try again ?
    Srini Chavali     @ Another "snapshot too old: rollback segment number  with name "" too small"
    Regards
    Girish Sharma

  • Segment number &  Numer of hierarchically higher SAP segment

    experts
    how to know the segment number &  Num of hierarchically higher SAP segment
    of the idocs?
    edi_dd-segnum -Number of SAP segment
    edi_dd-psgnum -Num of hierarchically higher SAP segment
    i have the problem in populating the hierarchy  and number of segment for orders05 idoc?
    ORDERS05                       Purchasing/Sales
           E1EDK01  IDoc: Document header general data
           E1EDK14  IDoc: Document Header Organizational Data
           E1EDK03  IDoc: Document header date segment
           E1EDK04  IDoc: Document header taxes
           E1EDK05 IDoc: Document header conditions
           E1EDKA1  Doc: Document Header Partner Information
               E1EDKA3                        IDoc: Document Header Partner Information Additional Data
           E1EDK02                        IDoc: Document header reference data
           E1EDK17                        IDoc: Document Header Terms of Delivery
           E1EDK18                        IDoc: Document Header Terms of Payment
           E1EDK35                        IDoc: Document Header Additional Data
           E1EDK36                        IDOC: Doc.header payment cards
           E1EDKT1                        IDoc: Document Header Text Identification
               E1EDKT2                        IDoc: Document Header Texts
           E1EDP01                        IDoc: Document Item General Data
           E1CUCFG                        CU: Configuration data
           E1EDL37                        Handling unit header
           E1EDS01                        IDoc: Summary segment general.

    thanks for the reply Alexander.
    i checked in we30, after clicking on the segment in the pop up box we can see
    the herichey level ie hlevel of the segment.
    Now how to know the segnum(segment number) of the segment?
    actually i am populating EDI_DD40, so i need the segnum.
    In edi_dd40 we have following
    SEGNAM = name of segment ex E1EDK01
    MANDT = sy-mandt
    DOCNUM = no need because i am generating idoc
    SEGNUM = ? I want to know from where i can get this
    PSGNUM = ? I want to know from where i can get this
    HLEVEL= this can be seen in we30
    SDATA = this is the fields we need to fill .
    so experts tell me from where i need to get psgnum and segnum?

  • Inconsistency between a document field and the prof. segment number

    Hi,
    While processing an invoice in one company code for vendor# XXX with the PO# AAAA line# 10, it is showing below error message while posting. Please advise on the below error or fix the issue to post the invoice in to SAP. The using screen T-code is miro.
    Inconsistency between a document field and the prof. segment number
    *Message no. KE396
    *Diagnosis
    A line item was assigned to a profitability segment (number 0008629207) which has the value 0000101000 for characteristic Profit Center. The original document (FI document, sales order, internal order, etc.), however, contains 0000102020 in this field. It is therefore inconsistent with the profitability segment found.
    System response
    The characteristics in Profitability Analysis (CO-PA) must have the same characteristic values as the original document. For example, you cannot assign a sales order to a different customer or product than the one contained in the original sales order. If you wish to fill the characteristics with different contents, you must change the original fields.
    Procedure
    Enter the correct characteristic values on the CO-PA assignment screen. The system will automatically assign a corresponding profitability segment number. If it is not possible to enter values in some of these fields, delete the entire assignment to a profitability segment number and then enter it again.
    As a rule, you should first enter the fields in the original sender document and then make the assignment to a profitability segment.
    What should I do for the above pl ?
    Regards
    Murali

    Hi,
    While doing PGR at VL32N, we are facing this error. Can someone assist.
    Regards,
    Aruna

  • Profitability segment number 02209 does not exist in operating concern ESAA

    Hello Experts,
    Please help us on one issue which  we are facing here that
    "Profitability segment number 02209 does not exist in operating concern ESAA"
    please could you please let us know why are facing this issue and where to check if this Profitability segment number.
    Thanks and Regards,
    Mangal Modi

    HI,
    This can occur if you have deleted data from table CE41001 and have
    already assigned data to profitability segments in this operating
    concern.
    Check the OSS note: 93051, hope it may help you..
    Thanks

  • Budget / Planning document number range per CO area

    Hi,
    I am facing the Issue for the budget and planning document number range.
    We are having 3 co area's in one server. I want to seperate it out the the number range for the planning and budgeting documents specific to co area.
    Please advice to do the same.
    Also the same issue with Claims numbers. How to resolve this.
    regards,

    Hi Friend,
    we are also check the no. range consistency & their is no inconsitenacy. what happen in COBK that it update the co document number range in a sequence. but in NRIV table it skip hundred & take the above number range. it mean CO document number & Current Number status which differ in COBK & NRIV table. why it happen we coundnt understand?
    can we maintain co document number range yearly?
    Warm Regards,
    Dhananjay R.

  • Planned order number - MFBF - Backflush

    Hi, Expert.
    In t-code MFBF in th field "planned order number" where and how I can put in this field as mandatory.
    I appreciate any help on this subject and also a step by step to implement, if possible
    Best Regards
    Armando

    Dear Armando,
    Even i faced this problem in one of my project
    User used to Backflush material level instead of plan order level
    But client requirement is user should only backflush via Plan order level
    so we made Via SHD0, plan order field mandatory & Material field as Display mode
    Plz check the below link for SHD0 & provide it to your Abaper
    [https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/transactionVariant-AStepbyStepGuidefor+Creation]
    Regards
    Madhu

  • Get planned order number(PLNUM) or requirement number(RSNUM) of a BOM item

    Hi everyone!
    I have a material...viewing it at MD16..i can now see the stock/requirements list displayed in a tree. Now i have below hierarchy:
    material 1       ----> has                planned order number
           material 2  ------> has           requirement number
                 material 3  ------> has       planned order/requirement number
                 material 4  ------>  has       planned order/requirement number
    material 5 ------> has       planned order
    material 6 ------> has       planned order
    using the planned order number of material 1 in the BOM, i was able to get the requirement number of material 2, what i want to know is how to get the requirement number of the next level under material 2...that is, the planned order/requirement number of material 3, material 4 ....
    thanks!
    Edited by: abapGenin on Jun 1, 2009 5:11 AM

    I answered this myself.
    I used  MD_SALES_ORDER_STATUS_REPORT.

  • System Error:Database access error,rollback segment number with name "" too small

    Hi Experts,
    In SXMB_MONI  XML messages for File2File scenario are failing
    with the below message:
    Database access error
    com.sap.aii.utilxi.misc.api.ResourceException: ORA-01555: snapshot too
    old: rollback segment number with name "" too small ORA-22924: snapshot
    too old at com.sap.aii.utilxi.blob.api.AIIBlob.getByteArray
    (AIIBlob.java:85) at
    com.sap.aii.utilxi.blob.api.AIIBlobImpl.getByteArray
    (BlobServices.java:156)
    I have refered this link http://scn.sap.com/thread/3147106
    Kindly suggest,
    Gagan.

    This may be due memory issue on the server. refer the note/thread as
    http://scn.sap.com/thread/3456694
    3807  - Error messages regarding rollback and undo segments
    Regards
    Ramg

Maybe you are looking for