Multiple materials input to planning board

Hi,
does anyone know if there is a way to specify multiple materials ( for instance thru copy/paste ) in the planning board MF52???
Any help appreciated !
danny

Hi Danny,
I don't think there is, but as you see, you could create a product group for these materials, and use it to access the planning table.
Regards,
Mario

Similar Messages

  • Ability to display multiple texts within graphic planning board Gantt chart

    I have been unable to change the planning board Bar Chart Graphic Profile (OPG0 and OPG9) to be able to display both material text and a user field within the Gantt chart graphic.  I have copied the SAPSFCG011 profile and created my own.  The profile is displayed below from CMCH.
    Overall prof: ZBWSFCG011           SFC: View work center/capacity (3 graf.)
    ...... Select.profile:                     ZBWSFCS001      SFC: View work center -> cap.(3 graf.)
    ...... Control profile:                    ZBW___C002      Gen: Planning table
    ...... Time prof:                           ZBW___Z002      Gen: Medium-term (3 months)
    ...... Evaluation prof.:                 ZBW___A001      Gen: Standard evaluation profile
    ...... Strategy prof.:                    ZBW___T001      Finite scheduling forw./all functs.activ
    ...... Capacity planning table:      ZBWSFCL010      SFC: only main cap. (3 graf.)
    .......... Graphics profile                      ZBW___X002      BARC    1  Default profile 2 Capa. planning board
    .......... Chart sequence                      ZBWSFCT002      SFC: Main caps. (3 graph.)
    .......... Layout ID                                 ZBWSFCLA10      SFC: Work center view     (graphical)
    .......... LineRepresSelection                 ZBW___ZR02      SAP standard 2
    .......... Scale time axis                         SAP___M031      Stand. weekly per. split rough
    .......... Graph.object.select.                ZBW___OA02      Pool group order path
    .............. DStat Sq Structur Field na ROp Comparison val NStat Struct
    .............. 00000 01 KBED     TYPKZ    NE  1                      00001
    .............. 00000 02 AFVG     OBJNR    ST  SAP005         00000 SAP002 Standard operation partially confirmed
    .............. 00000 03 AFVG     OBJNR    ST  SAP006         00000 SAP003 Standard operation completely confirmed
    .............. 00000 99                   DEF                                  00000 ZJB000 Standard operation
    ................... Graphical object type               ZJB000          Standard operation
    ........................ Form type                           22              Plan. board:Graphic obj. w. ordNo matTxt
    ........................... Form group                          ZBW001
    ............................... Form definition                     PLTO22          Planning board graphic order and mat.txt
    .................................. Layout definition                   [[$a//$b]]
    .................................. Layout definition
    .................................. Layout definition
    .................................. Layout definition
    In addition to the profile change, I have configured the graphical object type ZJB000 (in OPG9) to look as follows:
    0     AFKO     Order header                          MATXT     Material description                                                                     
    2     KBED     Capacity requirements     A     SSTAD     Latest start / date     SSTAU     Latest start / time
    3     KBED     Capacity requirements     A     SSSBD     Latest scheduled start: Processing (date)     SSSBZ     Latest scheduled start: Processing (time)
    4     KBED     Capacity requirements     A     SSSAD     Latest scheduled start: Teardown (date)     SSSAZ     Latest scheduled start: Teardown (time)
    5     KBED     Capacity requirements     A     SENDD     Latest finish / date     SENDU     Latest finish / time
    6       AFVG    Order operation                       USR08    User field for date                                                                               
    I have found that the 2nd text field (USR08) must be added as the last step (#6).  When I had it as #1, the planning board did not display the USR08 value.
    Now both are displayed in the Gantt chart graphic.  However, it is difficult to see this long string of data as the bars in the Gantt chart may not be long enough to display the data. 
    Therefore we would like to use the "hover over" text which is displayed in the status line at the bottom of the screen.  We have tried using both the Info Text and the Quick Info options within the Bar Chart: Options Profile (OPG0).  Only the first text (the material descirption) is dislayed within either the Quick Info or the Info Text.
    Is it possible to have multiple object values appear in Quick Info or Info Text?  Or is it possible to control which text is displayed in the Quick Info or Info Text?
    Any help in this area would be greatly appreciated, as this is a make-or-break issue for the business to use the planning board.  Thank you!

    I'm also looking for a standard customizing alternative to do the same thing.
    Still, if you're interested, I've already done it successfully with user exit PLAT0001.
    Hope this helps.
    Best regards.

  • MRS (Multi Resource Scheduling) - Show operation status in Planning Board

    Because the current MRS thread is some long and complicated I chose to move this question into a seperate thread:
    Initial question:
    Like many companies, it is not unusual at my customer for their Planners to create orders with multiple operations, particularly since many orders require different crafts to perform the work. When the Planning Board is launched and Planners lok at work scheduled for the past week they want to be able to see at a glance which operations have been completed and which operations, perhaps from the same order, have not and may need to be rescheduled. Their preference is to select "final confirmation" when using transaction IW41 and thereby set the operation system status to CNF when the work on an operation has been completed. They then want to somehow use this CNF operation status to drive something visual in the graphical Demand layout display and Resource layout display to enable the Planner to see at a glance that the operation has been completed. I've tried several approaches with configuration of abstract statuses and the user interface profile without success. My customer's interest in being able to see the completion status of an operation in the MRS Planning Board makes a lot of sense to me. I'm hoping someone can help me with a technique for modifying the Planning Board so that it displays the completion status of an operation in a visual way.
    Response from Varun Verma:
    Hi Mark,
    The problem at your customers end is nothing new.
    What you can do ( many other customers have done it in similar way ) is:
    1) you integrate the status CNF into MRS.
    Check the customizing: Basic Settings -> Assign ERP Objects -> Status
    2) configure in MRS that for status CNF, the assignments and demands (only in item work list or Hotlist) is colored to GREEN (or any other color)
    Check customizing: Set Up Scheduler Workplace -> Workplace Profiles -> Define User Interface Profiles
    Thus the users will know visually, that the green colored assignments are already completed.
    By the way, in your work list you can also filter the demands based on their status
    Regards
    Varun.
    Followup question:
    Varun,
    Thanks for the response.  I thought I had tried this but perhaps it's because in the UI profile I had not entered something in both the status groups for assignments and the status groups for demands.  I have a bit more testing to do but it appears that the demand status now gets updated from the operation status of PCNF (linked to abstract status WORK_START) and CNF (linked to abstract status WORK_STOP).  I also get a red bar (C4) for PCNF and a green bar (C1) for CNF.  Do you have a better status group I should be using in place of C1 and C4?  Status groups C1 and C4 give me a bar but it doesn't look like the demand bar with a outline and alphanumeric description of the demand, it's just a colored bar.
    I know the work list can be filtered based on their MRS "planning" status, however, it doesn't appear to permit filtering by the status of the operation unless I add the operation status as an additional field in the worklist.  Is there something I'm missing here?  And even if it did, my customer wants to be able to see the CNF status indication in the Demand layout and schedule using the work centers so the worklist is not being shown like it is in the Resource layout.
    Mark
    Edited by: Mark Scott on Aug 10, 2009 3:35 PM

    Hi Mark,
    Well I assumed that you have confirmations integration active !! But I guess not because you say that the status is not integrated always.
    What you need to do:
    1) I assume you have SP05 or later.
    2) Implement the user exit: CONFPM05. In the implementation of this exit you need to call FM: /MRSS/RSG_PM_ORDER_CONFIRM
    3) Go to customizing: Basic Settings --> Assign ERP Objects --> Status
      -- Here, define an abstract status (MRS Status) for confirmed and partially confirmed
      -- map it to R3 status CNF and PCNF.
    After this, whenever you enter confirmation for PM order from transaction IW41, the status will be integrated.
    Now you can use the MRS statuses defined in step 3 to configure the colors.
    Implementing the user exit CONFPM05 might require some technical input. But it is easy. Just a few double clicks and copy paste.
    Contact an ABAP developer for the same.
    This should solve your issue.
    Regards
    Varun

  • Usb 6009 multiple analog inputs

    I am currently attempting to sample two different analog inputs at different sampling rates using a USB 6009.  I keep getting the 'resource reserved' error and am wondering if this is not possible using this DAQ.  Questions:
    1.  Does creating two analog input channels on the device cause this error?
    2.  Is it possible to sample at different rates on channels created in the same task?  (i am trying to 'slow down' the second analog input to display switch points to a customer)
    3.  Running multiple analog inputs using independent timing would be better achieved by switching to a higher end DAQ?  If so which would you recommend?
    I have attached my vi.  Thank you in advance for your help. 
    I surf therefore I am....
    Attachments:
    demo_nolvl.vi ‏27 KB

    The DAQ boards only have 1 timing clock for the analog inputs/outputs.  So you can only have 1 sample rate on a given card.  I would recommend just sampling at the highest of the desired rates in a single task.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Creation of Order in DS Planning Board (/SAPAPO/CDPS0)

    Hi all,
    My requirement is i want to create order manually in DS planning board by passing product, location,resource,runlength etc.
    Again i am using PPM to calculate the setup time (between previous order and the current order).
    In order to get the PPM data, i am calling FM "/SAPAPO/DM_PPM_GET_PLAN" and here i pass planid to get the details.
    To get planid, i call FM "/SAPAPO/SOS_FIND" i.e. to get source of supply information which includes planid
    Please tell me
    (1) what is planid ?
    (2) How planid is this linked to PPM ?
    (3) What do we mean by sources of supply? Can't we get the same info from pegid ?
    (4) What is the structure of PPM ? I mean what are activities, components, alternative components etc.
    Regards,
    Deb

    Hi Nandha / Vikas
    Thanks for your input.
    I am summerizing the whole concept, Please correct me and answer my questions in between :-
    In order to create an order in DS Planning board manually, we need information like product,location,resource,quantity etc. (User's input).
    Then we should follow the steps as follows -:
    Step 1 :- Find Sources of Supply
    Since this gives information like how we are going to produce or procure the product. It can be PPM or PDS or Transportation lane.
    For PPM we will get the Plan id (Unique ID for PPM) and then we will get the details of PPM accordingly.
    But, Please mention what about PDS and Transportation lane ?
    I mean from source of supply how can we know that the product can be produced or procured by PPM or PDS or Transportation lane ? Any field indicator is there for PPM or PDS or Transportation lane? Because in my requirement, First i need to check which one is active for the entered product:- PPM or PDS.
    (2) Once we know that the source of supply is PPM or PDS or transaportation lane, then we will call different FMs to get the details.
    For PPM we know how to proceed. I mean using planid we can get the details.
    But for PDS and Transaportation lane please mention the FM name and i/p parameters to get the details like setup group id, production rate etc.
    Thnaks once again for your valuable inputs.
    Deb

  • MD04 but for multiple materials

    Hi,
    Would just like to ask is there a standard report that lists down planning results for multiple materials?
    It's like Stock/Requirements List (MD04) but for multiple materials....the info/fields I need are the ones found in MD04.
    Thanks.
    Best Regards,
    Armie

    Dear Armie,
    You can't see MD04 details for multiple materials. Actually, it is impossible because MD04 is a screen designed for a single material.
    However, if you want multiple material planning details, you would use
    function LM61XU11 MD_STOCK_REQUIREMENTS_LIST_API to collect your own data and display it.
    Regards,
    Onat

  • MD03 for multiple materials

    Hi Friends,
    I want to execute MD03 with multiple materials (15 or 20 selective materials), also i want save this as variant and run every hour. 
    How could i make this? Any user exit is there to do this?
    Please help.
    Thanks
    Srini

    Hi,
    You can use the User Exit: M61X0001
    With this you need to get the Coding done from your ABAPer such that it will consider your Materials..
    With this the criteria can be considerd is:
    materials to be planned using MRP procedures,
    materials of a certain MRP controller
    externally procured materials or materials produced in-house
    With MD01/MDBT you can use the User Exit Key (which you will define in OMIX) and Plan every houre as per your requirement..
    Regards,
    Siva

  • Unicode in Project Planning Board Screen (CJ20N)

    Hi,
    I'm facing a problem of unicode as follows:
    I inputed some unicode (Vietnamese) at Project Structure screen, It is ok. but when I switch to Project Planning Board screen, It don't work. I also cannot input Vietnamese with unicode at this view.
    Text example: "Các công tác chuẫn bị"
    Please help!
    Thanks
    Long

    Hi,
    Found something on Service.sap.com
    Thought would be useful..
    To access this page you need a login id for service.sap.com
    https://websmp108.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000557148&
    thanks..

  • Ignore PPM Mode Linkage in Planning Board

    Hello experts,
    I have a a burning question here..
    I'm working in a project whose using PPDS PPM with more than one activities, and multiple modes (for alternative resources). In the Activity Relationship, we define Mode Linkage as '3', so whenever we schedule an operation in Planning Board, the predecessor operation will be scheduled according to the mode relationship in PPM.
    There is a requirement to break the 1-1 mode relationship for exceptional planning during short term period. Without changing the Mode Linkage, can we break the relationship in Planning Board using a specific PP/DS strategy?
    *Hope my question is clear enough
    Thanks
    Yudhia

    Hi Santosh,
    Thanks for the reply.
    When I changed the Order Int-Rel to Do Not Consider, I couldnt move any order (inlcuding dep.orders) to alternative resource.
    So now, I'm using Order-Int.Rel = Always Consider and I have the flexibility to move it to alternative resource.
    But the problem is that I think it always read the Mode Linkage in PPM. Whenever I move the dependant order to it's alternative resource, the parent order will also moved accoring to mode relationship.
    Whereas the requirement it to break the relationship for exceptional case.
    Regards
    Yudhia

  • Unicode in Planning Board Screen (CJ20N)

    Hi,
    I'm facing a problem of unicode as follows:
    I inputed some unicode (Vietnamese) at Project Structure screen, It is ok. but when I switch to Project Planning Board screen, It don't work. I also cannot input Vietnamese with unicode at this view.
    Text example: "Các công tác chuẫn bị"
    Please help!
    Thanks
    Long

    Hi,
    Found something on Service.sap.com
    Thought would be useful..
    To access this page you need a login id for service.sap.com
    https://websmp108.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000557148&
    thanks..

  • Bug when dealing with multiple file input elements?

    I'm running Apex 4.2 and have an odd problem.
    Back Story:
    I have created a page on a standard web server (Apache) that allows a user to select multiple images from there local machine. The form reads one file at a time displaying a preview of the image and reading the exif data from the file.  We are entering extra data about each picture into a form.  So the flow of the page is: user selects images -> first image is displayed and user enters data -> submits data via ajax -> user hits button and next image comes up.  The user repeats until all images are done.  I have not done the ajax portion but all other parts work fine on the Apache server.
    The Problem:
    I need to recreate this type of form in Apex.   If I create a multiple file input item on a page all the tabs stop working.  They take you to a 404 page with the message "The requested URL /apex/wwv_flow.accept was not found on this server ".  I have tracked it back to anything calling the apex.submit() javascript function. 
    Literally if I make a html region and place "<input id="uploadInput" type="file" name="myFiles" multiple>"  into the region source the apex.submit() function stops working.
    Any thoughts?

    Epic Fail wrote:
    Literally if I make a html region and place "<input id="uploadInput" type="file" name="myFiles" multiple>"  into the region source the apex.submit() function stops working.
    Any thoughts?
    Not a bug. The file browse control you have created cannot be processed by the APEX wwv_flow.accept procedure that performs page submit processing. Your control's name attribute is myFiles, but there is no corresponding parameter in wwv_flow.accept:
    -- A C C E P T
    -- This procedure accepts virtually every flow page.
    -- Reference show procedure for input argument descriptions.
    procedure accept (
        p_request      in varchar2  default null,
        p_instance      in varchar2  default null,
        p_flow_id      in varchar2  default null,
        p_company      in number    default null,
        p_flow_step_id  in varchar2  default null,
        p_arg_names    in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_arg_values    in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_arg_checksums in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_page_checksum in varchar2                default null,
        p_accept_processing in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v01          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v02          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v03          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v04          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v05          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v06          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v07          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v08          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v09          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v10          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v11          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v12          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v13          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v14          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v15          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v16          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v17          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v18          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v19          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v20          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v21          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v22          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v23          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v24          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v25          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v26          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v27          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v28          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v29          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v30          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v31          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v32          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v33          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v34          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v35          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v36          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v37          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v38          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v39          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v40          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v41          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v42          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v43          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v44          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v45          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v46          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v47          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v48          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v49          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v50          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v51          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v52          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v53          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v54          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v55          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v56          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v57          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v58          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v59          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v60          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v61          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v62          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v63          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v64          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v65          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v66          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v67          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v68          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v69          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v70          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v71          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v72          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v73          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v74          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v75          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v76          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v77          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v78          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v79          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v80          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v81          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v82          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v83          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v84          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v85          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v86          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v87          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v88          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v89          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v90          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v91          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v92          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v93          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v94          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v95          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v96          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v97          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v98          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v99          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v100          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v101          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v102          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v103          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v104          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v105          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v106          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v107          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v108          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v109          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v110          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v111          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v112          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v113          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v114          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v115          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v116          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v117          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v118          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v119          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v120          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v121          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v122          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v123          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v124          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v125          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v126          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v127          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v128          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v129          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v130          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v131          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v132          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v133          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v134          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v135          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v136          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v137          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v138          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v139          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v140          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v141          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v142          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v143          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v144          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v145          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v146          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v147          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v148          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v149          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v150          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v151          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v152          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v153          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v154          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v155          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v156          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v157          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v158          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v159          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v160          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v161          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v162          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v163          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v164          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v165          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v166          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v167          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v168          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v169          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v170          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v171          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v172          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v173          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v174          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v175          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v176          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v177          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v178          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v179          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v180          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v181          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v182          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v183          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v184          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v185          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v186          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v187          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v188          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v189          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v190          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v191          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v192          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v193          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v194          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v195          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v196          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v197          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v198          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v199          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_v200          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_t01          in varchar2  default null,
        p_t02          in varchar2  default null,
        p_t03          in varchar2  default null,
        p_t04          in varchar2  default null,
        p_t05          in varchar2  default null,
        p_t06          in varchar2  default null,
        p_t07          in varchar2  default null,
        p_t08          in varchar2  default null,
        p_t09          in varchar2  default null,
        p_t10          in varchar2  default null,
        p_t11          in varchar2  default null,
        p_t12          in varchar2  default null,
        p_t13          in varchar2  default null,
        p_t14          in varchar2  default null,
        p_t15          in varchar2  default null,
        p_t16          in varchar2  default null,
        p_t17          in varchar2  default null,
        p_t18          in varchar2  default null,
        p_t19          in varchar2  default null,
        p_t20          in varchar2  default null,
        p_t21          in varchar2  default null,
        p_t22          in varchar2  default null,
        p_t23          in varchar2  default null,
        p_t24          in varchar2  default null,
        p_t25          in varchar2  default null,
        p_t26          in varchar2  default null,
        p_t27          in varchar2  default null,
        p_t28          in varchar2  default null,
        p_t29          in varchar2  default null,
        p_t30          in varchar2  default null,
        p_t31          in varchar2  default null,
        p_t32          in varchar2  default null,
        p_t33          in varchar2  default null,
        p_t34          in varchar2  default null,
        p_t35          in varchar2  default null,
        p_t36          in varchar2  default null,
        p_t37          in varchar2  default null,
        p_t38          in varchar2  default null,
        p_t39          in varchar2  default null,
        p_t40          in varchar2  default null,
        p_t41          in varchar2  default null,
        p_t42          in varchar2  default null,
        p_t43          in varchar2  default null,
        p_t44          in varchar2  default null,
        p_t45          in varchar2  default null,
        p_t46          in varchar2  default null,
        p_t47          in varchar2  default null,
        p_t48          in varchar2  default null,
        p_t49          in varchar2  default null,
        p_t50          in varchar2  default null,
        p_t51          in varchar2  default null,
        p_t52          in varchar2  default null,
        p_t53          in varchar2  default null,
        p_t54          in varchar2  default null,
        p_t55          in varchar2  default null,
        p_t56          in varchar2  default null,
        p_t57          in varchar2  default null,
        p_t58          in varchar2  default null,
        p_t59          in varchar2  default null,
        p_t60          in varchar2  default null,
        p_t61          in varchar2  default null,
        p_t62          in varchar2  default null,
        p_t63          in varchar2  default null,
        p_t64          in varchar2  default null,
        p_t65          in varchar2  default null,
        p_t66          in varchar2  default null,
        p_t67          in varchar2  default null,
        p_t68          in varchar2  default null,
        p_t69          in varchar2  default null,
        p_t70          in varchar2  default null,
        p_t71          in varchar2  default null,
        p_t72          in varchar2  default null,
        p_t73          in varchar2  default null,
        p_t74          in varchar2  default null,
        p_t75          in varchar2  default null,
        p_t76          in varchar2  default null,
        p_t77          in varchar2  default null,
        p_t78          in varchar2  default null,
        p_t79          in varchar2  default null,
        p_t80          in varchar2  default null,
        p_t81          in varchar2  default null,
        p_t82          in varchar2  default null,
        p_t83          in varchar2  default null,
        p_t84          in varchar2  default null,
        p_t85          in varchar2  default null,
        p_t86          in varchar2  default null,
        p_t87          in varchar2  default null,
        p_t88          in varchar2  default null,
        p_t89          in varchar2  default null,
        p_t90          in varchar2  default null,
        p_t91          in varchar2  default null,
        p_t92          in varchar2  default null,
        p_t93          in varchar2  default null,
        p_t94          in varchar2  default null,
        p_t95          in varchar2  default null,
        p_t96          in varchar2  default null,
        p_t97          in varchar2  default null,
        p_t98          in varchar2  default null,
        p_t99          in varchar2  default null,
        p_t100          in varchar2  default null,
        p_t101          in varchar2  default null,
        p_t102          in varchar2  default null,
        p_t103          in varchar2  default null,
        p_t104          in varchar2  default null,
        p_t105          in varchar2  default null,
        p_t106          in varchar2  default null,
        p_t107          in varchar2  default null,
        p_t108          in varchar2  default null,
        p_t109          in varchar2  default null,
        p_t110          in varchar2  default null,
        p_t111          in varchar2  default null,
        p_t112          in varchar2  default null,
        p_t113          in varchar2  default null,
        p_t114          in varchar2  default null,
        p_t115          in varchar2  default null,
        p_t116          in varchar2  default null,
        p_t117          in varchar2  default null,
        p_t118          in varchar2  default null,
        p_t119          in varchar2  default null,
        p_t120          in varchar2  default null,
        p_t121          in varchar2  default null,
        p_t122          in varchar2  default null,
        p_t123          in varchar2  default null,
        p_t124          in varchar2  default null,
        p_t125          in varchar2  default null,
        p_t126          in varchar2  default null,
        p_t127          in varchar2  default null,
        p_t128          in varchar2  default null,
        p_t129          in varchar2  default null,
        p_t130          in varchar2  default null,
        p_t131          in varchar2  default null,
        p_t132          in varchar2  default null,
        p_t133          in varchar2  default null,
        p_t134          in varchar2  default null,
        p_t135          in varchar2  default null,
        p_t136          in varchar2  default null,
        p_t137          in varchar2  default null,
        p_t138          in varchar2  default null,
        p_t139          in varchar2  default null,
        p_t140          in varchar2  default null,
        p_t141          in varchar2  default null,
        p_t142          in varchar2  default null,
        p_t143          in varchar2  default null,
        p_t144          in varchar2  default null,
        p_t145          in varchar2  default null,
        p_t146          in varchar2  default null,
        p_t147          in varchar2  default null,
        p_t148          in varchar2  default null,
        p_t149          in varchar2  default null,
        p_t150          in varchar2  default null,
        p_t151          in varchar2  default null,
        p_t152          in varchar2  default null,
        p_t153          in varchar2  default null,
        p_t154          in varchar2  default null,
        p_t155          in varchar2  default null,
        p_t156          in varchar2  default null,
        p_t157          in varchar2  default null,
        p_t158          in varchar2  default null,
        p_t159          in varchar2  default null,
        p_t160          in varchar2  default null,
        p_t161          in varchar2  default null,
        p_t162          in varchar2  default null,
        p_t163          in varchar2  default null,
        p_t164          in varchar2  default null,
        p_t165          in varchar2  default null,
        p_t166          in varchar2  default null,
        p_t167          in varchar2  default null,
        p_t168          in varchar2  default null,
        p_t169          in varchar2  default null,
        p_t170          in varchar2  default null,
        p_t171          in varchar2  default null,
        p_t172          in varchar2  default null,
        p_t173          in varchar2  default null,
        p_t174          in varchar2  default null,
        p_t175          in varchar2  default null,
        p_t176          in varchar2  default null,
        p_t177          in varchar2  default null,
        p_t178          in varchar2  default null,
        p_t179          in varchar2  default null,
        p_t180          in varchar2  default null,
        p_t181          in varchar2  default null,
        p_t182          in varchar2  default null,
        p_t183          in varchar2  default null,
        p_t184          in varchar2  default null,
        p_t185          in varchar2  default null,
        p_t186          in varchar2  default null,
        p_t187          in varchar2  default null,
        p_t188          in varchar2  default null,
        p_t189          in varchar2  default null,
        p_t190          in varchar2  default null,
        p_t191          in varchar2  default null,
        p_t192          in varchar2  default null,
        p_t193          in varchar2  default null,
        p_t194          in varchar2  default null,
        p_t195          in varchar2  default null,
        p_t196          in varchar2  default null,
        p_t197          in varchar2  default null,
        p_t198          in varchar2  default null,
        p_t199          in varchar2  default null,
        p_t200          in varchar2  default null,
        f01            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f02            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f03            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f04            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f05            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f06            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f07            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f08            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f09            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f10            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f11            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f12            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f13            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f14            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f15            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f16            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f17            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f18            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f19            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f20            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f21            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f22            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f23            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f24            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f25            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f26            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f27            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f28            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f29            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f30            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f31            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f32            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f33            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f34            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f35            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f36            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f37            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f38            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f39            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f40            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f41            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f42            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f43            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f44            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f45            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f46            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f47            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f48            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f49            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        f50            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        fcs            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        fmap            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        fhdr            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        fcud            in wwv_flow_global.vc_arr2 default empty_vc_arr,
        frowid          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        x01            in varchar2  default null,
        x02            in varchar2  default null,
        x03            in varchar2  default null,
        x04            in varchar2  default null,
        x05            in varchar2  default null,
        x06            in varchar2  default null,
        x07            in varchar2  default null,
        x08            in varchar2  default null,
        x09            in varchar2  default null,
        x10            in varchar2  default null,
        x11            in varchar2  default null,
        x12            in varchar2  default null,
        x13            in varchar2  default null,
        x14            in varchar2  default null,
        x15            in varchar2  default null,
        x16            in varchar2  default null,
        x17            in varchar2  default null,
        x18            in varchar2  default null,
        x19            in varchar2  default null,
        x20            in varchar2  default null,
        p_listener      in wwv_flow_global.vc_arr2 default empty_vc_arr, -- used to communicate with apex listner
        p_map1          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_map2          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_map3          in wwv_flow_global.vc_arr2 default empty_vc_arr,
        p_survey_map    in varchar2  default null,
        p_flow_current_min_row      in varchar2 default '1',
        p_flow_current_max_rows    in varchar2 default '10',
        p_flow_current_rows_fetched in varchar2 default '0',
        p_debug                    in varchar2 default 'NO',
        p_trace                    in varchar2 default 'NO',
        p_md5_checksum              in varchar2 default '0',
        p_page_submission_id        in varchar2 default null,
        p_time_zone                in varchar2 default null,
        p_ignore_01    in varchar2 default null,
        p_ignore_02    in varchar2 default null,
        p_ignore_03    in varchar2 default null,
        p_ignore_04    in varchar2 default null,
        p_ignore_05    in varchar2 default null,
        p_ignore_06    in varchar2 default null,
        p_ignore_07    in varchar2 default null,
        p_ignore_08    in varchar2 default null,
        p_ignore_09    in varchar2 default null,
        p_ignore_10    in varchar2 default null,
        p_lang          in varchar2 default null,
        p_territory    in varchar2 default null)
    The normal approach to creating forms in APEX is to use declarative page items, or to create items dynamically using the apex_item API. APEX knows how to process these items because they are generated with names matching wwv_flow.accept parameters, but not manually created controls with arbitrary name attributes.
    Are you planning on doing all of your form submission via AJAX? (I doubt that APEX will be able to natively handle a file browse control with a multiple attribute.) If so, remove the name="myFiles" attribute. You will still be able to access the control in JS using the ID, but APEX won't see it.

  • Locate Materials with Future Planned Price

    Hi All,
    I have a user who did costing run in between of the month to change the Standard price from next month and Marked the prices for next month but forgot to note down the Material numbers.
    Now, the problem is in the month of July'14 when CK24 is executed for release no materials are coming up. It is possible that the Costing entered is for the month of June'14.
    Is there any report by which we can locate materials which Future Planned price and period and Current Planned Price and Period.
    Regards

    Hi,
    It is  very simple,
    You will get all price results in the table MBEW:
    For your query relevant field is : ZPLPR.
    Go to SE16: MBEW table and provide the input of your plant and execute.
    Check whether there are any entries in ZPLPR,
    If you find entries in that filed means materials marked for the estimate but it was yet to be released.
    you will get the total list of materials.
    Please find the relevant tables and fields to get the prices in the material master:
    Let me know if you find any difficulty to get the values in the table
    Regards,
    Pavan Kumar Arvapally

  • Mass assignment of materials to Inspection Plan

    All,
    Is there any standard transaction or BAPI/BADI to assign multiple materials viz 1000 plus to an Inspection plan.
    Thanks
    Anup

    You have two option to upload mass materials to inspection plan.
    Option1: Go to QP02 --> Material assignment screen. Here you can assign 14 materials at a time and do page down to assign next 14 materials. This is time consuming activity.
    Option2: With help of techinical person develop LSMW/ BADI which call QP02 to update material assignment in inspection plan.
    Please find few relavent descussion below, I hope it will help you take decisioon.
    [mass assigning of inspection plans]
    [Mass Assign Material to Inspection Plan]
    [Re: Mass material assignment  in Inspection Plan.]

  • Pool asset management planning board (PAM03)

    Hi experts,
    PAM03 comes with default icons/labels for vehicle pooling. For example in the tool bar there is a filter for 'licence plate' or 'vehicles' for sorting. As you know the PAM can be used for variety of assets such as IT. I wanted to know if you've ever attempted to update the planning board to be used for assets other than vehicles.
    I believe in note 1272432 there is mention to this functionality using function module PAMS_GRAPH_UC_OTHERS. I'm still trying to figure out how this works so any input is appreciated.
    Thanks

    Hi PAM user, the steps necessary for PAM are described in the following places, at the sap Help portal
    http://help.sap.com/erp2005_ehp_04/helpdata/en/2b/1a73268dd74a0988c00a90171294f7/frameset.htm
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/0b/5ad2c9e2f249abad4df1479243a001/frameset.htm
    Make sure you activate the SAP Business Function for PAM, which is LOG_EAM_PAM (via transaction SFW5). This will also provide the right settings within config for the planning board and Pool Asset Management.
    Only thing that does not automatically gets updates, is table PAMS_VSTAI, which needs to have the following entries:
    Pool Asset Management   ABGH    04      Productive Split        I3908   Picked Up
    Pool Asset Management   AUFE     02      Completed Split I3910   Settled
    Pool Asset Management   DISP       01      Productive Split        I3902   Assigned
    Pool Asset Management   GELA              Completed Split I3905   Deleted by requestor
    Pool Asset Management   GELD              Completed Split I3903   Deleted by planner
    Pool Asset Management   NDIS      01      Reqmt   I3901   Need
    Pool Asset Management   RESM    06      Productive Split        I3907   Reserved
    Pool Asset Management   RGBE    03      Completed Split I3909   Returned
    Pool Asset Management   STAN    05      Completed Split I3906   Need revoked
    Pool Asset Management   STOR    05      Completed Split I3904   Planned need revoked
    Pool Asset Management   SY01    08      Absence         Maintenance/ Repair
    Pool Asset Management   SY02    07      Absence         End of Leasing
    I hope this helps you in setting up the solution. Feel free to provide feedback on if it worked.
    Cheers,
    Hanneke

  • Pool Asset Management- Planning Board

    Hi Guys,
    We are in the process of implementing PAM in our company.
    I have done the config based on the note ; 1272432 up to certain extent. When i go to PAM03-planning board, the following message is appearing " Illegal number of columns in chart(231, 1, 0), Sum of columns in chart is not equal".
    I could not able to find the configuration part for this.
    Also in the planning table, i could able to see the request, but i am not able to see the equipments assigned to Pool (functional location category).
    Kindly provide your valuable inputs.
    Thanks&Regards,
    Pavan

    Hi PAM user, the steps necessary for PAM are described in the following places, at the sap Help portal
    http://help.sap.com/erp2005_ehp_04/helpdata/en/2b/1a73268dd74a0988c00a90171294f7/frameset.htm
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/0b/5ad2c9e2f249abad4df1479243a001/frameset.htm
    Make sure you activate the SAP Business Function for PAM, which is LOG_EAM_PAM (via transaction SFW5). This will also provide the right settings within config for the planning board and Pool Asset Management.
    Only thing that does not automatically gets updates, is table PAMS_VSTAI, which needs to have the following entries:
    Pool Asset Management   ABGH    04      Productive Split        I3908   Picked Up
    Pool Asset Management   AUFE     02      Completed Split I3910   Settled
    Pool Asset Management   DISP       01      Productive Split        I3902   Assigned
    Pool Asset Management   GELA              Completed Split I3905   Deleted by requestor
    Pool Asset Management   GELD              Completed Split I3903   Deleted by planner
    Pool Asset Management   NDIS      01      Reqmt   I3901   Need
    Pool Asset Management   RESM    06      Productive Split        I3907   Reserved
    Pool Asset Management   RGBE    03      Completed Split I3909   Returned
    Pool Asset Management   STAN    05      Completed Split I3906   Need revoked
    Pool Asset Management   STOR    05      Completed Split I3904   Planned need revoked
    Pool Asset Management   SY01    08      Absence         Maintenance/ Repair
    Pool Asset Management   SY02    07      Absence         End of Leasing
    I hope this helps you in setting up the solution. Feel free to provide feedback on if it worked.
    Cheers,
    Hanneke

Maybe you are looking for