Routings List

Has anyone written query to show routing lists. In a column format. Similiar to the information shown in CA51.
Thank you

Closing thread no answer

Similar Messages

  • Define own no ranges for Boms & Routings(task list type)

    hello all,
    I need to confirm if we can have seperate no ranges for materials Boms or routings on the same client?
    I think we can assign a new Bom no range but can't have different no ranges for different material boms on the same system. Moreover, using CS90 we can only define the internal no range for material boms?
    For task list we can define external no ranges but this gets assigned to the task list types. Is it possible to define our own task list type? I don't think so, but not a 100% sure.
    Pls can somebody confirm this for me.
    Many thanks.

    hi
    what you mentioned is correct there is no option of creating the task list types and also of youcan have external number ranges for BOMs check t-code SNUM with object STUE.
    -ashok

  • LSMW Error in loading ROUTINGS

    Hi Experts,
    I am getting a error at step 13 while creating Batch input session using LSMW as "No Profile with entry tool task list N 1 session ROUTING".
    I tried to use the default value for BIPKO-PRFIDNETZ = (default value tht i was given).still it says same error.
    any idea...plz help me out...
    I'm using 0170 RCPTRA01 prg.
    Thanks
    Sony

    Hi,
    Maintain a profile in which the entry tool is activated in field BIPKO-PROFIDNETZ of the input file.
    You make settings for the entry tool in the control data for routings within Customizing under Production -> Basic Data -> Routing -> Control Data -> Define profiles with default values.
    Activate the entry tool
    Save the long text and set it to active.
    Cheers
    VJ
    Do a search in OSS notes you will find more info

  • How to get the workcentres used in the routing out of 2 alternate routings

    Dear All,
    I would like to know how to get the workcentres used in the routing out of 2 alternate routings.
    I referred PLKO got the Task List Type (PLNTY), Group(PLNNR), Group Counter(PLNAL), Plant(werks).
    I passed this in to PLPO, The problem in PLPO is we don’t have the distinguishing field Group Counter(PLNAL), so I am getting all the ARBID including both alternates.
    How to get the ARBID with respect to Groupcounter 1 alone.
    If a get the ARBID , I can get the ARBPL from CRHD.

    HI,
    Use PLAS Table also.  you have to use PLKO> PLAS> PLPO.
    Pass PLNNR & PLNAL in PLAS and get PLNNR & PLNKN.
    Then pass these into PLPO.
    work centers from CRHD
    Regards,
    Krishna Mohan
    Edited by: Krishna Mohan N on Jan 31, 2008 12:28 PM

  • Trying to delete a routing task list (N) and getting an error on CA98

    Getting an error when trying to delete a task list routing without archiving using t-code CA98. 
    Error:       "Task list 01184667 01 (type 01184667) is still used in inspection lots"
    The inspection lot is for a production order. The routing I am trying to delete was used in that production order.
    I found the inspection lot and there is a UD of accept on it but I cannot delete the task list routing.
    If I archived the task list routing for the material and tried to delete the task list routing would I still get the same error as above?
    Tom

    You can use CA98 only for test data which you no longer intend to use or refer to. I don't think even CA99(with archiving) can help here. Please check the dependencies for deletion of routings: [http://help.sap.com/saphelp_47x200/helpdata/en/7e/d41b73455911d189400000e8323c4f/content.htm]
    Thanks,
    Anil

  • Report name for services where used in task lists

    plz let me know report name for services  where used in task lists.

    Hello Sairam,
    I am abit confused. Are you looking for report to find where the task list is used ? You can find all the available reports in The menu path Logistics -> Production -> Master Data -> Routings -> Reporting.
    If you want a specific one then please provide more details
    Thanks
    Amber

  • Matl. where used list

    Hi Frndz,
    what is the t. code to see material where used report?
    I want to see usage of matls in BOM,Routings, Pro.orders and also it's qty. in stock at a glance.
    Thanks in advance,
    Rohit.

    Dear Rohit,
    You can get the material where used for a single material using T Code CS15, and prepare a report to check the same for a
    multiple list of materials using this FM,
    CS_WHERE_USED_MAT or else CSEP_MAT_BOM_SELECT_WHERE_USED.
    Regards
    Mangalraj.S

  • Not Updating Operations when Uploading Routings

    Hi All,
    I am using Direct Input method to upload routings using LSMW. When i finished all steps in LSMW i am getting mesage that "Routing is updated in group XXXXXXXX" with Message type I. I have'nt seen the operations for that Routing when i tried to view in CA03. Shall i have to upload the operations separately for  routing. If so then why we have to map the plpo_di_ds structure.

    Did you map the structures:
    BIPPO Batch input structure for task list operation
    and
    BIPTX Batch input structure for long texts for routings

  • Planned Orders (Independent) to standard routings

    Hi Experts,
    Is there any link between planned orders and standard routings. If there's any, please indicate.
    Thanks and points will be given,
    LM

    Hi Leo
    Planned orders are the result of MRP run or can also be created manually - they are kind of a proposals before you convert the Planned order to a Prodcution order or a Preq depending on the business scenario.
    Standard Routings are part of master data needed to create a Prodcution order- it is the combnation of the Bill Of Material and the task list.
    Please let me know if you need any more information on this.
    Thanks
    Deepak

  • Upload Routings - LSMW

    Ok experts, really need you help with this one.  I'm upload routings via direct input program RCPTRA02 in LSMW.  I need to attach an object dependecy to the operation.  I think that I have all the field values that I need, but it does not update when the routings is created.  Everthing else is there except for the assigned object dependency.  Anyone have any clue what I'm missing here?  I implemented a note that I thought would help, but it didn't.  Really need some help with this one....
    Here is a look at my LSMW structure that I'm using for the assignment of dependencies.
    RCUOB1_DS                      Assignment of dependencies in DIRECT INPUT (datasets)                                                                               
    5  Fields                                                                               
    ACTTYP                       Processing type for objects to be imported                                              
                                Rule :   Constant                                                                               
    Coding:  RCUOB1_DS-ACTTYP = 'H'.                                                                 
            OBJ                          Data objects of a task list                                                                               
    Rule :   Constant                                                                               
    Coding:  RCUOB1_DS-OBJ = 'O'.                                                                    
            PLNAL                        Group counter                                                                               
    Rule :   Constant                                                                               
    Coding:  RCUOB1_DS-PLNAL = '01'.                                                                 
            PLNFL                        Sequence                                                                               
    Rule :   Constant                                                                               
    Coding:  RCUOB1_DS-PLNFL = '000000'.                                                             
            VORNR                        Operation/Activity Number                                                                               
    Source:  ROUTINGSD-OPERATION (operation)                                                                               
    Rule :   Transfer (MOVE)                                                                               
    Coding:  RCUOB1_DS-VORNR = ROUTINGSD-OPERATION.                                                  
            VORKN                        Node number (batch input)                                                               
            UVORN                        Operation/Activity Number                                                                               
    Rule :   Constant                                                                               
    Coding:  RCUOB1_DS-UVORN = ''.                                                                   
            UVOKN                        Node number (batch input)                                                               
            PSNFH                        Item number of the production resource/tool (batch input)                               
            PZLFH                        Counter for production resource/tool items (batch input)                                
            KN_AL_FROM                   Character field length = 10                                                             
            KN_AL_TO                     Character field length = 10                                                                               
    5  RCUOB2_DS                      API structure for dependency assignments (for datasets)                                                                               
    5  Fields                                                                               
    KNNAM                        Name of dependency                                                                               
    Source:  ROUTINGSD-OBJDEP (Object Dependency)                                                                               
    Rule :   Transfer (MOVE)                                                                               
    Coding:  RCUOB2_DS-KNNAM = ROUTINGSD-OBJDEP.                                                 
                XKNNAM                       Name of dependency                                                                               
    Source:  ROUTINGSD-OBJDEP (Object Dependency)                                                                               
    Rule :   Transfer (MOVE)                                                                               
    Coding:  RCUOB2_DS-XKNNAM = ROUTINGSD-OBJDEP.                                                
                KNSRT                        Counter for sorting object assignments (Batch-Input)                                
                LKENZ                        Deletion indicator                                                                               
    Regards,
    Rich Heilman

    Ok, I got it.  I knew it had to be something simple.  Here I need to have a kind of couter(from and to) 
    <b>
    KN_AL_FROM                   Character field length = 10                                      
                       Coding:  * Target field: RCUOB1_DS-KN_AL_FROM Character field length = 10 
                                 RCUOB1_DS-KN_AL_FROM = sy-tabix.                                 
    KN_AL_TO                     Character field length = 10                                      
                        Coding:  RCUOB1_DS-KN_AL_TO = sy-tabix. </b>                                  
    I set these counters to sy-tabix, and now all is well. Works very good now.   I've tested with mulitple operations per routing and mulitple routings.  No problems.  Thanks for the replies anyway.
    It was note 526351  .
    Regards,
    Rich Heilman

  • About Query of Routings

    Hi,
    I've met a serious problem,could anyone help me out?Here's the situation:
    I used MAPL (PLNTY,PLNNR,PLNAL,ZAEHL)>PLKO (PLNTY,PLNNR,PLNAL,ZAEHL)>PLAS (PLNTY,PLNNR,PLNKN,ZAEHL)>PLPO (ARBID)>CRHD to set up a query,searching routings by Mats.
    Now I can use this query normally when seraching the routings batchly inputted initially before the system operated,but when searching the newly mannually set-up routings(CA01),the results can only show the first operations.
    Y would this happen and how could I handle this?
    Edited by: Leo Zheng on Dec 21, 2007 3:07 AM

    Hi Leo,
    The reason is if u create a routing for first time in CA01, it will be updated in PLKO and the some value is assigned to the  field ZAEHL  ex 1 .
    If u change the routing in CA02 it will not be updated in PLKO. if u add one opeartion to the routing , the filed  value (ZAEHL)should have increased to 2, this will  not happen. So it remains as 1. But in PLPO the second opeartion will be updated with ZAEHL is 2.
    So while data fetching, only one value is (ZAEHL=1) passed from PLKO->PLAS->PLPO.
    This would result u will get always first opertion only in the output. If u remove that Field Link from PLKO->PLAS-PLPO,then   u will get the all operation list same as CA02.
    i hope this clear ur doub, if do plsease close the thread.
    Regards
    Pradeep
    Edited by: Pradeep Kumar on Dec 25, 2007 3:52 PM

  • Creating Routings via LSMW

    Hi all,
    Can anyone give me some pointers when creating Routings via LSMW. I see there are two standard uploads in RCPTRA01 and RCPTRA02. However, the mapping structures seem to be different between the two.
    I need to add PRT's material assignments and long texts to the routing.
    Any help greatly appreciated.

    Hi,
    Use standard batch/Direct input : RCPTRA02
    Source Fields
            MATERIAL_ROUTING          Material
                PLNAL                          C(002)    Group Counter
                MATNR                          C(018)    Article Number
                WERKS                          C(004)    Site
                OPERATION_ROUTING         Operations
                    PLNAL                          C(002)    Group Counter
                    VORNR                          C(004)    Operation/Activity Number
                    STEUS                          C(004)    Control Key
                    ARBPL                          C(008)    Work center
                    WERKS                          C(004)    Site
                    LTXA1                          C(040)    Operation short text
                    MEINH                          C(003)    Quantity unit for operation (batch input)
                    BMSCH                          C(017)    Base quantity (Batch input)
                    LAR02                          C(006)    Activity Type
                    VGE02                          C(003)    Unit for the standard value (batch input)
                    VGW02                          C(011)    Standard Value (Batch Input)
                    LAR03                          C(006)    Activity Type
                    VGE03                          C(003)    Unit for the standard value (batch input)
                    VGW03                          C(011)    Standard Value (Batch Input)
                COMPONENT_ROUTING         Components
                    PLNAL                          C(002)    Group Counter
                    VORNR                          C(004)    Operation/Activity Number
                    POSNR                          C(004)    BOM Item Number
                    MATNR                          C(018)    Article Number
                    WERKS                          C(004)    Site
    Field Mapping and Rule
           RC271_DS                       Work center structure for direct input (for datasets)
               Fields
                   TCODE                        Transaction Code
                                       Rule :   Constant
                                       Code:    RC271_DS-TCODE = 'CA01'.
                   STTAG                        Character Field Length = 10
                                       Rule :   Constant
                                       Code:    RC271_DS-STTAG = '18.03.2014'.
                   AENNR                        Change Number
                   REVLV                        Revision Level
                   WERKS                        Site
                                       Rule :   Transfer (MOVE)
                                       Code:    RC271_DS-WERKS = MATERIAL_ROUTING-WERKS.
                   PROFIDNETZ                   Profile
                   PLNNR                        Key for Task List Group
                   PLNAL                        Group Counter
                                       Rule :   Transfer (MOVE)
                                       Code:    RC271_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
                   STATU                        Status
                                       Rule :   Constant
                                       Code:    RC271_DS-STATU = '4'.
                   VAGRP                        Responsible Planner Group/Department
                                       Rule :   Constant
                                       Code:    RC271_DS-VAGRP = 'KD1'.
                   VBELN                        Sales Document
                   POSNR                        Character field of length 6
                   PSPNR                        Work Breakdown Structure Element (WBS Element)
    MAPL_DI_DS                     Assign routing to article for direct input (for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Code:    MAPL_DI_DS-ACTTYP = 'H'.
            MATNR                        Article Number
                                Rule :   Transfer (MOVE)
                                Code:    MAPL_DI_DS-MATNR = MATERIAL_ROUTING-MATNR.
            WERKS                        Site
                                Rule :   Transfer (MOVE)
                                Code:    MAPL_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    MAPL_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
            LIFNR                        Vendor Account Number
            KUNR                         Account Number of Customer
            SUCHFELD                     Search Field for Customer-Specific Task List Selection
            VBELN                        Sales Document
            POSNR                        Sales Document Line Item (Batch Input Field)
            PSPNR                        Work Breakdown Structure Element (WBS Element)
    PLKO_DI_DS                     Header structure for direct input (for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Code:    PLKO_DI_DS-ACTTYP = 'H'.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    PLKO_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
            VERWE                        Use by user or system
                                Rule :   Constant
                                Code:    PLKO_DI_DS-VERWE = '1'.
            WERKS                        Site
                                Rule :   Transfer (MOVE)
                                Code:    PLKO_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
            STATU                        Status
                                Rule :   Constant
                                Code:    PLKO_DI_DS-STATU = '4'.
            PLNME                        Unit of measure for the task list (batch input)
                                Rule :   Constant
                                Code:    PLKO_DI_DS-PLNME = 'KG'.
            LOSVN                        From lot size (BTCI)
                                Rule :   Constant
                                Code:    PLKO_DI_DS-LOSVN = '0'.
            LOSBS                        To lot size (BTCI)
                                Rule :   Constant
                                Code:    PLKO_DI_DS-LOSBS = '999999999'.
            VAGRP                        Responsible planner group/department
                                Rule :   Constant
                                Code:    PLKO_DI_DS-VAGRP = 'KD1'.
            KTEXT                        Task list description
                                Rule :   Constant
                                Code:    PLKO_DI_DS-KTEXT = 'Article Routing'.
            TXTSP                        Single-Character Indicator
    PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Code:    PLPO_DI_DS-ACTTYP = 'H'.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-PLNAL = OPERATION_ROUTING-PLNAL.
            PLNFL                        Sequence
                                Rule :   Constant
                                Code:    PLPO_DI_DS-PLNFL = '000000'.
            VORKN                        Node number (batch input)
            VORNR                        Operation/Activity Number
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-VORNR = OPERATION_ROUTING-VORNR.
            UVOKN                        Node number (batch input)
            UVORN                        Suboperation
            STEUS                        Control key
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-STEUS = OPERATION_ROUTING-STEUS.
            ARBID                        Object ID (batch input)
            OBJTY                        Object types of the CIM resource
            ARBPL                        Work center
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-ARBPL = OPERATION_ROUTING-ARBPL.
            WERKS                        Site
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-WERKS = OPERATION_ROUTING-WERKS.
            KTSCH                        Standard text key
            LTXA1                        Operation short text
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-LTXA1 = OPERATION_ROUTING-LTXA1.
    MEINH                        Quantity unit for operation (batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-MEINH = OPERATION_ROUTING-MEINH.
    UMREN                        Denominator for conversion from unit to base unit (BTCI)
                        Rule :   Constant
                        Code:    PLPO_DI_DS-UMREN = '1'.
    UMREZ                        Numerator for converting from unit to base unit (BTCI)
                        Rule :   Constant
                        Code:    PLPO_DI_DS-UMREZ = '1'.
    BMSCH                        Base quantity (Batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-BMSCH = OPERATION_ROUTING-BMSCH.
    ZMERH                        Break time (batch input)
    ZEIER                        Unit for break time (batch input)
    LAR01                        Activity Type
    VGE01                        Unit for the standard value (batch input)
    VGW01                        Standard Value (Batch Input)
    LAR02                        Activity Type
    VGE02                        Unit for the standard value (batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGE02 = OPERATION_ROUTING-VGE02.
    VGW02                        Standard Value (Batch Input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGW02 = OPERATION_ROUTING-VGW02.
    LAR03                        Activity Type
    VGE03                        Unit for the standard value (batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGE03 = OPERATION_ROUTING-VGE03.
    VGW03                        Standard Value (Batch Input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGW03 = OPERATION_ROUTING-VGW03.
    PLMZ_DI_DS                     Article component allocation for direct input(for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-ACTTYP = 'H'.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    PLMZ_DI_DS-PLNAL = COMPONENT_ROUTING-PLNAL.
            PLNFL                        Sequence
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-PLNFL = '000000'.
            PLNKN                        Node number (batch input)
            VORNR                        Operation/Activity Number
                                Rule :   Transfer (MOVE)
                                Code:    PLMZ_DI_DS-VORNR = COMPONENT_ROUTING-VORNR.
            STLTY                        BOM category
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-STLTY = 'M'.
            STLNR                        Bill of material
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-STLNR = '00000005'.
            STLAL                        Alternative BOM
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-STLAL = '01'.
            STLKN                        Node number (batch input)
            POSNR                        BOM Item Number
                                Rule :   Transfer (MOVE)
                                Code:    PLMZ_DI_DS-POSNR = COMPONENT_ROUTING-POSNR.
    WERKS                        Site
                        Rule :   Transfer (MOVE)
                        Code:    PLMZ_DI_DS-WERKS = COMPONENT_ROUTING-WERKS.
    BOMAT                        Article Number
                        Rule :   Transfer (MOVE)
                        Code:    PLMZ_DI_DS-BOMAT = COMPONENT_ROUTING-MATNR.
    STLST                        Order level
    STLWG                        Order path
    STLTY_W                      BOM category
                        Rule :   Constant
                        Code:    PLMZ_DI_DS-STLTY_W = 'M'.
    STLNR_W                      Bill of material
                        Rule :   Constant
                        Code:    PLMZ_DI_DS-STLNR_W = '00000005'.
    STLAL_W                      Alternative BOM
                        Rule :   Constant
                        Code:    PLMZ_DI_DS-STLAL_W = '01'.
    Map the extra fields according to your requirement. Hope you'll find the code helpful.

  • Usage Only Routings in Work centers in Plant maintenance

    Dear Gurus,
    My client wanted only one work center and usage only maintenance task list in begining. Now they want to chage to Only Routings usage. I want to know what is it and what impact it will have now if I changed.
    Regards,
    PMaddi

    The Usage field in the work centre only controls which type of task list or routings the work centre can be used in.
    In your case, if you use 002, then you will not be able to use that work centre in a task list or order
    PeteA

  • List of materials with valid Group Counters (No. of valid routing variant)

    Hi,
    do you know, how to get a list of the materials together with the information, what Group Counter is currently valid? That means if a material have 3 variants of routings, to show for example that the variant number 3 is currently valid.
    Thank you in advance.
    Ivana

    Hi Sankaran,
    this is a great tip. I tried it but it seems that our engineering has some "strange" rules for creating of the group counters. There were several group counters for one material that had the same Valid From date:-( I will have to discuss with them, why they do so.
    However thank you very much for your help. I´m satisfied what I got from the C223 transaction.
    Have a nice day.
    Ivana

  • CK40N Error List

    Hi Experts
    Can anybody provide me the list of errors that might come up like something related std.price, BOM, Routings etc while we run CK40N.
    Thank you

    Hi,
    Please try to use T-code OPR4_CK.
    Regards,
    Polla

Maybe you are looking for

  • View a single table-row as multiple rows in a GridControl

    Hi, is it possible to distribute the entries of a single row of a table/RowSetInfo over multiple lines of a GridControl? I've seen an example on the Internet (http://www2.gol.com/users/tame/swing/examples/JTableExamples4.html) which does this without

  • Bulk Update query

    Hello Friends, Can some one suggest me is that any possible bulk update query which consumes less timings? Table - MyTable id - PK. orderid - Order Id. Subid - Sub Id for an Order. lineitem - LineItemId. ProducId - Product Id. Now i want to update th

  • Event name in SAP Portal

    Dear all, I need to know what the different event name for allowin  iViews to communicate with each other and with the portal environment itself . Example EPCM.subscribeEvent("urn:com.sapportals:navigation", "Navigate", pop);                   In abo

  • SortFolders() Token throws an invalid operation error

    Hello, I have a big trouble with the SortFolder() token which simply isn't recognized by the GroupwiseCommander. I just want to alphabetically sort a folder's subfolders and the Object API doesn't give me any way to do it, as far as I've seen. The pr

  • Locking Text to a screen position...

    Does anyone know where I can find a tutorial about how to lock one layer to another...meaning, if it's text over a handheld shot, the text moves with the shot. Short of keyframing each frame individually, (which doesn't look great) I'm not sure how t