Material Manufacturing with in the Workshop of Maintenance Department

Dear SAP Gurus,
The Client has the following scenario:
In case of some materials such as shafts, bearing etc. if any of such material gets defective, the material is forwarded to the workshop who with some raw materials invent the replica of the same material. Now as the material is created it is routed through the substore to the location of desired maintenance. How to capture this scenario. What movement type could be used?
Regards,
Muhammad Usman Kahoot

There are various movement types that could be used.Consult your MM consultant for config associated to the same. Generally a Production order is created and posted into Stock but if PP hasn't been configured have a look at standard movement types between 500 and 550.
Regards
Narasimhan

Similar Messages

How to Issue Material To Maintenance Department

Hello Expert,
      I want to know how to issue material to maintenance department in SAP B1.
      Tell me detail procedure. My client want process in SAP B1.
      He told me the material he want is available in store but store department not issue material becoz there is no doc to tell store department to issue material to maintenance department.
     Please give me solution as early as possible.
     Thanks in Advance.
Regards,
Sandy

Hi Sandesh,
Try this below method which am doing for one of our client,
Create one Warehouse called Maintenance.
When ever maintenance department needs, material they have to request through "Inventory Transfer Request". Take a print and give to stores department
Using this Request , Stores department can transfer the stock to Maintenance department.
If it is consumed then , Maintenance department have to do "Goods Issue", Items like Oil , Grease etc..
If the items is going out the company for the Service , then create one warehouse called "Service" and do "Inventory transfer" to that warehouse.
If the material is come back, then do "Inventory Transfer" using Ctrl + Tab from Service warehouse to Maintenance warehouse.
Let me know if you need any clarification of the above points.

To fill in the material number with item category u201CBu201D for Framework Order.

The use of framework orders (also referred to as blanket purchase orders) enables you to procure a variety of materials or services from a vendor up to a predefined maximum value (the value limit).
Instead of a specific delivery date, you specify a validity period for the order.
Goods receipts or the entry and acceptance of services performed are not necessary in the case of a framework PO and limit items.
The invoices are posted directly with reference to the purchase order, provided that the specified value limit is not exceeded. When the value limit of the PO is reached, or the validity period is exceeded, the system issues a warning message. It is possible to book the invoices, but these are blocked for payment.
During the phase of service performance, the cumulative u201Cactual" values (for the services actually performed) are continually updated in the underlying purchase. This enables you to monitor the progress of a procurement project on an ongoing basis. By comparing the "actual" value with the total value, you can always obtain an overview of the degree to which a budget for unplanned services or materials has been exhausted (i.e. see whether predefined limits have been reached or nearly reached).
So with the Framework Order type (FO) and item category u201CBu201D you get the error that it is not allowed to fill in the material number with item category u201CBu201D.
Please suggest me the possible solution to fill in the material number with item category u201CBu201D for Framework Order.
Best Regards,
Harisha

The Framework order type is specialy defined for lesser value procurements (ex: stationeries, cleaning services ....) which are all not worthy to create Material Master at all.
If you are very sure to fill the Material number, then proceed with some other document type.
In what circumstances you want to put material number in FO order?
Karthi.

Creating Materialized View with the Distinct key word

Hi
I need help to create Materialized View with the Distinct key word.
my query is
select distinct col1, col2 from t1;
is there any alternate of DISTINCT because I can not refresh the MV as fast on demand if I am using it and Fast on Demand is a must for me.

hi
check out this link
http://download-west.oracle.com/docs/cd/B12037_01/server.101/b10736/basicmv.htm#i1007299
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/intro.htm#sthref183
hope this helps
CHeers

Creating a material with just the basic view using BAPI

Hi
   I intend to create a new material with just the basic view using BAPI BAPI_MATERIAL_SAVEDATA -
To do this - I believe I have to fill in the structure HEADDATA data - ( mandatory ) with the required values - I fill values for fields IND_SECTOR, MATL_TYPE & basic view ( check this field ) and leave the MATERIAL field as blank (assuming internal numbering ) and then fill values of the CLIENTDATA structure with values for the basic data view.
Is this correct ? Will my material number created be returned in the RETURN structure - how do I look for the material number exclusively in my RETURN structure ?

hi
good
go through this progarm which ll give you detail idea about BAPI_MATERIAL_SAVEDATA
REPORT ZBAPIMM01 LINE-SIZE 255 NO STANDARD PAGE HEADING
                 LINE-COUNT 065(001).
TABLES: T001L, "Storage Locations
        MARA, "General Material Data
        MAKT, "Material Descriptions
        MBEW, "Material Valuation
        MARC. "Plant Data for Material
DATA: BAPI_HEAD   LIKE BAPIMATHEAD,
      BAPI_MAKT   LIKE BAPI_MAKT,    "Material Description
      BAPI_MARA1 LIKE BAPI_MARA,    "Client Data
      BAPI_MARAX LIKE BAPI_MARAX,
      BAPI_MARC1 LIKE BAPI_MARC,    "Plant View
      BAPI_MARCX LIKE BAPI_MARCX,
      BAPI_MBEW1 LIKE BAPI_MBEW,    "Accounting View
      BAPI_MBEWX LIKE BAPI_MBEWX,
      BAPI_RETURN LIKE BAPIRET2.
DATA: BEGIN OF INT_MAKT OCCURS 100.
        INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF INT_MAKT.
DATA: BEGIN OF INT_MAT OCCURS 100,
         WERKS(4),     "Plant
         MTART(4),     "Material type
         MATNR(18),    "Material number
         MATKL(9) ,    "Material group
         MBRSH(1),     "Industry sector
         MEINS(3),     "Base unit of measure
         GEWEI(3),     "Weight Unit
         SPART(2),     "Division
         EKGRP(3),     "Purchasing group
         VPRSV(1),     "Price control indicator
         STPRS(12),    "Standard price
         PEINH(3),     "Price unit
         SPRAS(2),     "Language key
         MAKTX(40),     "Material description
       END OF INT_MAT.
SELECT-OPTIONS:
            PLANT    FOR MARC-WERKS OBLIGATORY MEMORY ID PLT,
            MATERIAL FOR MARA-MATNR MEMORY ID MAT,
            MATLTYPE FOR MARA-MTART MEMORY ID MTY,
            DIVISION FOR MARA-SPART MEMORY ID DIV.
PARAMETERS: F_FILE LIKE RLGRAP-FILENAME
             DEFAULT 'C:\DATA\ZMATERIAL.XLS' MEMORY ID F_FILE,
             GETDATA AS CHECKBOX, "Tick to download materials data to local harddisk
             UPDDATA AS CHECKBOX. "Tick to update date to Materials Master
IF GETDATA = 'X'.
   PERFORM DOWNLOAD_DATA.
   PERFORM DOWNLOAD_FILE.
ENDIF.
IF UPDDATA = 'X'.
   PERFORM UPLOAD_FILE.
   PERFORM UPDATE_MM.
ENDIF.
FORM DOWNLOAD_DATA.
SELECT * FROM MARC WHERE LVORM EQ ' '
                      AND WERKS IN PLANT
                      AND MATNR IN MATERIAL.
    CLEAR MARA.
    SELECT SINGLE * FROM MARA WHERE MATNR = MARC-MATNR.
    CHECK MATLTYPE.
    CHECK DIVISION.
    CLEAR MBEW.
    SELECT SINGLE * FROM MBEW WHERE MATNR = MARC-MATNR
                                AND BWKEY = MARC-WERKS.
    CLEAR MAKT.
    SELECT SINGLE * FROM MAKT WHERE SPRAS = 'EN'
                                AND MATNR = MARC-MATNR.
    WRITE:/ MARC-WERKS,    "Plant
            MARA-MTART,    "Material type
            MARA-MATNR,    "Material number
            MARA-MATKL,    "Material group
            MARA-MBRSH,    "Industry sector
            MARA-MEINS,    "Base unit of measure
            MARA-GEWEI,    "Weight Unit
            MARA-SPART,    "Division
            MARC-EKGRP,    "Purchasing group
            MBEW-VPRSV,    "Price control indicator
            MBEW-STPRS,    "Standard price
            MBEW-PEINH,    "Price unit
            MAKT-SPRAS,    "Language key
            MAKT-MAKTX.    "Material description
            INT_MAT-WERKS = MARC-WERKS.    "Plant
            INT_MAT-MTART = MARA-MTART.    "Material type
            INT_MAT-MATNR = MARA-MATNR.    "Material number
            INT_MAT-MATKL = MARA-MATKL.    "Material group
            INT_MAT-MBRSH = MARA-MBRSH.    "Industry sector
            INT_MAT-MEINS = MARA-MEINS.    "Base unit of measure
            INT_MAT-GEWEI = MARA-GEWEI.    "Weight Unit
            INT_MAT-SPART = MARA-SPART.    "Division
            INT_MAT-EKGRP = MARC-EKGRP.    "Purchasing group
            INT_MAT-VPRSV = MBEW-VPRSV.    "Price control indicator
            INT_MAT-STPRS = MBEW-STPRS.    "Standard price
            INT_MAT-PEINH = MBEW-PEINH.    "Price unit
            INT_MAT-SPRAS = MAKT-SPRAS.    "Language key
            INT_MAT-MAKTX = MAKT-MAKTX.    "Material description
            APPEND INT_MAT.
            CLEAR INT_MAT.
ENDSELECT.
ENDFORM.
FORM DOWNLOAD_FILE.
call function 'WS_DOWNLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Download Successfully to your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPLOAD_FILE.
call function 'WS_UPLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Upload Successfully from your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPDATE_MM.
LOOP AT INT_MAT.
Header
    BAPI_HEAD-MATERIAL        = INT_MAT-MATNR.
    BAPI_HEAD-IND_SECTOR      = INT_MAT-MBRSH.
    BAPI_HEAD-MATL_TYPE       = INT_MAT-MTART.
    BAPI_HEAD-BASIC_VIEW      = 'X'.
    BAPI_HEAD-PURCHASE_VIEW   = 'X'.
    BAPI_HEAD-ACCOUNT_VIEW    = 'X'.
Material Description
    REFRESH INT_MAKT.
    INT_MAKT-LANGU           = INT_MAT-SPRAS.
    INT_MAKT-MATL_DESC       = INT_MAT-MAKTX.
    APPEND INT_MAKT.
Client Data - Basic
    BAPI_MARA1-MATL_GROUP     = INT_MAT-MATKL.
    BAPI_MARA1-BASE_UOM       = INT_MAT-MEINS.
    BAPI_MARA1-UNIT_OF_WT     = INT_MAT-GEWEI.
    BAPI_MARA1-DIVISION       = INT_MAT-SPART.
    BAPI_MARAX-MATL_GROUP = 'X'.
    BAPI_MARAX-BASE_UOM   = 'X'.
    BAPI_MARAX-UNIT_OF_WT = 'X'.
    BAPI_MARAX-DIVISION   = 'X'.
Plant - Purchasing
    BAPI_MARC1-PLANT      = INT_MAT-WERKS.
    BAPI_MARC1-PUR_GROUP = INT_MAT-EKGRP.
    BAPI_MARCX-PLANT      = INT_MAT-WERKS.
    BAPI_MARCX-PUR_GROUP = 'X'.
Accounting
    BAPI_MBEW1-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEW1-PRICE_CTRL = INT_MAT-VPRSV.
    BAPI_MBEW1-STD_PRICE = INT_MAT-STPRS.
    BAPI_MBEW1-PRICE_UNIT = INT_MAT-PEINH.
    BAPI_MBEWX-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEWX-PRICE_CTRL = 'X'.
    BAPI_MBEWX-STD_PRICE = 'X'.
    BAPI_MBEWX-PRICE_UNIT = 'X'.
    WRITE:/ BAPI_HEAD, BAPI_MARC1.
    call function 'BAPI_MATERIAL_SAVEDATA'
      exporting
        HEADDATA                   = BAPI_HEAD
        CLIENTDATA                 = BAPI_MARA1
        CLIENTDATAX                = BAPI_MARAX
        PLANTDATA                  = BAPI_MARC1
        PLANTDATAX                 = BAPI_MARCX
      FORECASTPARAMETERS         =
      FORECASTPARAMETERSX        =
      PLANNINGDATA               =
      PLANNINGDATAX              =
      STORAGELOCATIONDATA        =
      STORAGELOCATIONDATAX       =
        VALUATIONDATA              = BAPI_MBEW1
        VALUATIONDATAX             = BAPI_MBEWX
      WAREHOUSENUMBERDATA        =
      WAREHOUSENUMBERDATAX       =
      SALESDATA                  = BAPI_MVKE1
      SALESDATAX                 = BAPI_MVKEX
      STORAGETYPEDATA            =
      STORAGETYPEDATAX           =
      IMPORTING
        RETURN                     = BAPI_RETURN
      TABLES
        MATERIALDESCRIPTION        = INT_MAKT
      UNITSOFMEASURE             =
      UNITSOFMEASUREX            =
      INTERNATIONALARTNOS        =
      MATERIALLONGTEXT           =
      TAXCLASSIFICATIONS         =
      RETURNMESSAGES             =
      PRTDATA                    =
      PRTDATAX                   =
      EXTENSIONIN                =
      EXTENSIONINX               =
IF BAPI_RETURN-TYPE = 'E'.
   WRITE:/ 'Error Message ', BAPI_RETURN.
ENDIF.
ENDLOOP.
ENDFORM.
*---End of Program
thanks
mrutyun^

SCCM fails to deploy Patches to client with in the maintenance windows.

Hi,
I am new to Patchng through SCCM just 7 months of experience.
I deploy the patches regular month basis as microsoft release the patches every month. till now the patch deployment was happening smoothly, but from last month i am facing issue like the SCCM failed to push the patches with in the provided maintenance window.
even if the maintenance window over client will not get install.
i have checked the enforcement status report for the same collection which i deployed, the status is always downloading updtaes.
We have collection called Workstation and servers, both the collections compliance is less like 20% or lesser than that.
Arround 800 Workstations deployed and given deadline 10 days. with suppressed reboot.
Arround 70 Servers deployed with with automatic reboot via Maintenance window.
deadline to install is 1 hour ahead of maintenance window.
It would be great if any one suggest the solution to make software update deployment through SCCM with in the maintenance window.

Vista is not a supported OS for Acrobat XI Pro.

How to trace Returnable packaging material pending with the Customer.

Hello Everyone,
In case of Returnable packaging,
Is there any standard procedure, by which system can give you number of returnable packaging material with the custome.
Client's requirement is to have number of pallets with the customer on the Invoice.
Regards
Trupti Deulkar

hi,
1.Returnable packging issue has a special stock indicator which will show in the Inventor stock with whom the returnable packging material lies in MMBE.
Follow the link
http://help.sap.com/saphelp_46c/helpdata/en/dd/560051545a11d1a7020000e829fd11/content.htm
Thanks
Shekar

With the Internet Explorer maintenance no longer in IE9 and above

Hi
I heard someone that With the Internet Explorer maintenance no longer in IE9 and above version of IE.
Is this True ?
As I have lots of GPO of favorites configured in IE maintenance and other as well..
Will they be not supportive any more..
If yes, what is the other solution for all my IE maintenance settings ?

IE maintenance has been deprecated with Group Policy Preferences (GPP), Administrative Templates (.admx), and the Internet Explorer Administration Kit 11 (IEAK 11).
More information:
http://idanve.blogspot.co.il/2014/07/configure-internet-explorer-10-or-11.html
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Import FOC(Free of Charge) PO (Manufacturing) with claimable duties

Dear SAP guru,
We're currently on 4.6C and implementing a project for India. We have a scenario for Import FOC(Free of Charge) PO (Manufacturing) with claimable duties.
Material price in Material Master = 10(Basic) + 5.00(Un claimable duties) + 3.00 (Freight)
The user would like to see the accounting postings below. Is it even possible to do that in MIGO? I am unable to save my PO when Net Value is Zero. Can you help?
MIGO
Raw Mat: 18.00 (Dr)
GR/IR Clearing: 0.00 (Cr)
Clearing of Duties: 5.00 (Cr) *unclaimable
Clearing of Freight: 3.00 (Cr)
Price Difference: 10.00 (Cr)
MIRO (No vendor invoice)
MIRO (Clearing invoice)
Clearing Agent: 3.00 (Cr)
Clearing of Freight: 3.00 (Dr)
MIRO (Customs invoice)
Customs: 10.00 (Cr)
Clearing of duties: 5.00 (Dr) *unclaimable
Clearing of duties: 10.00 (Dr) *claimable
regards,
Jules

Hi,
"Please check to :
SPRO - Materials Management - Purchasing - Purchase Order - Define Screen Layout at Document Level "
Think here we can maintain the fields for mandatory/display/optional w.r.to each transaction....but my question is why the error message in popping up...even though there is no invoice update indicator is marked.
BR,
Krishna

Skip the Creation of Maintenance Notification

I would like to know the effect if i will skip or remove the process of creation of Maintenance notification in SAP PM. The process will start with the creation of Order, if there's an external service required the Maintenance Order will be converted into PO if no external service or material will close the Order.
Since the Creation of Maintenance Order will generate Notification, we were thinking that creation of Notification is redundant if the system allows to create order and notification in one transaction.
What would be the effect of this, thanks and God bless.

Greetings Peach,
As the experts, who had already answered observed, this is purely a business process consideration. If your (Client's) organization supports a "streamlined" process in which direct Order creation is beneficial you can go for it.
As you've written "Since the Creation of Maintenance Order will generate Notification, we were thinking that creation of Notification is redundant if the system allows to create order and notification in one transaction." I assume you are still using Notification and Order integration. But as Yogesh Dhokne mentioned, this is optional as well.
If you choose to create a Notification in the background, you can still register breakdown times for MTTF/MTBF calculations, Catalog Codes for tracking and any additional information once the Orders are created.
But consider this: How is work requested, released for execution and reported? If you only create Orders, you have only Orders to go on. Therefore, you might require more verbose User Status management, and you may find yourself with Orders that are being created unnecessarily and have to be closed, Orders being released prematurely... You have to have a very "flat" process around this immediate Order creation.
On the other hand, consider that having Notifications created prior means a more "deep" process and more overhead, but you can have a step to filter works to be released on the Notification level before Orders are created, if you have more than one Notification for the same work, you can assign it to a single Order, and you have more options when designing roles and authorizations, since you can separate access and business transactions for Notifications and Orders for your Operations and Maintenance users, if necessary.
Please ask further questions if you have any!

Materialized View with Joins

Dear Dev/DBAs,
I have the following scenario:
SQL> CREATE TABLE T1 (ID NUMBER(3),NAME VARCHAR2(10));
SQL> CREATE TABLE T2 (ID NUMBER(3),NAME VARCHAR2(10));
The T1 contains records having the ID num from 10 to 80 and the T2 having the ID from 90 to 170
SQL> SELECT * FROM T1 JOIN ALL SELECT * FROM T2
It give all records in the 2 tables.
I'm planning to create a materialized view (like CREATE MATERIALIZED VIEW V_TAB REFRESH ON COMMIT AS SELECT * FROM T1 JOIN ALL SELECT * FROM T2) and it seems i can't do with the error ORA-12054, further the oracle documentation says that materialized view can only be used with a simple join.
Do you have another solution??
Note that the materialized views can be used to improve queries.
Thank you in advance

Straight from the link I posted:
*Restrictions on Fast Refresh on Materialized Views with UNION ALL*Materialized views with the UNION ALL set operator support the REFRESH FAST option if the following conditions are satisfied:
* The defining query must have the UNION ALL operator at the top level.
The UNION ALL operator cannot be embedded inside a subquery, with one exception: The UNION ALL can be in a subquery in the FROM clause provided the defining query is of the form SELECT * FROM (view or subquery with UNION ALL) as in the following example:
CREATE VIEW view_with_unionall AS
(SELECT c.rowid crid, c.cust_id, 2 umarker
FROM customers c WHERE c.cust_last_name = 'Smith'
UNION ALL
SELECT c.rowid crid, c.cust_id, 3 umarker
FROM customers c WHERE c.cust_last_name = 'Jones');
CREATE MATERIALIZED VIEW unionall_inside_view_mv
REFRESH FAST ON DEMAND AS
SELECT * FROM view_with_unionall;
Note that the view view_with_unionall satisfies the requirements for fast refresh.
* Each query block in the UNION ALL query must satisfy the requirements of a fast refreshable materialized view with aggregates or a fast refreshable materialized view with joins.
The appropriate materialized view logs must be created on the tables as required for the corresponding type of fast refreshable materialized view.
Note that the Oracle Database also allows the special case of a single table materialized view with joins only provided the ROWID column has been included in the SELECT list and in the materialized view log. This is shown in the defining query of the view view_with_unionall.
* The SELECT list of each query must include a maintenance column, called a UNION ALL marker. The UNION ALL column must have a distinct constant numeric or string value in each UNION ALL branch. Further, the marker column must appear in the same ordinal position in the SELECT list of each query block.
* Some features such as outer joins, insert-only aggregate materialized view queries and remote tables are not supported for materialized views with UNION ALL.
* Partiton Change Tracking (PCT)-based refresh is not supported for UNION ALL materialized views.
* The compatibility initialization parameter must be set to 9.2.0 or higher to create a fast refreshable materialized view with UNION ALL.

Materialized Views with Query Rewrite is not getting re-written

I have tried everything that has been mentioned in all the forums here and on metalink to fix this issue, has any smart APEX user found a solution?
The issue is the MV with Query rewrite capability is not being re-written.
Things I have tried
1) give all Query Rewrite privileges to all 3 APEx schemas and parsing schema;
2) check trace files with tkprof;
3) dynamically printed explain plan from v$_SQL on the page while executing the query;
4) to test in a different environment i created an another DAD using the pl/sql webtool kit and tried the same thing and rewrite works like a charm...
whats the issue here...why are apex schemas not re-writing the queries????
appreciate any help...thanks

Jes, per your request
--create materialized view
CREATE MATERIALIZED VIEW "RPLANSWEB"."MV_FCG_ALL_SUMMARY_TAB"
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 81920 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "RPLANSWEB"
BUILD IMMEDIATE
USING INDEX
REFRESH FORCE ON DEMAND
USING DEFAULT LOCAL ROLLBACK SEGMENT
ENABLE QUERY REWRITE
AS SELECT fcg, year, fcg_desc,
fac, efr, fac_desc, efr_desc,
ums_round, fcg_allow_drillable allow_drillable,
MAX(category_code_um1) category_code_um1,
SUM(perm_asset) perm_asset,
SUM(temp_asset) temp_asset,
SUM(semi_asset) semi_asset,
SUM(lease_asset) lease_asset,
SUM(planned_constr) planned_constr,
SUM(all_perm_asset) all_perm_asset,
SUM(total_asset) total_asset,
SUM(allow) allow, SUM(rqmt) rqmt,
SUM(perm_planned_constr) perm_planned_constr,
SUM(perm_planned_constr_rqmt_delta) perm_planned_constr_rqmt_delta,
ROUND(DECODE(SUM(rqmt), 0, 0, SUM(all_perm_asset)/SUM(rqmt)*100)) perm_rqmt_pctsat,
ROUND(DECODE(SUM(allow), 0, 0, SUM(all_perm_asset)/SUM(allow)*100)) perm_allw_pctsat,
ROUND(DECODE(SUM(rqmt), 0, 0, SUM(total_asset)/SUM(rqmt)*100)) total_rqmt_pctsat,
ROUND(DECODE(SUM(allow), 0, 0, SUM(total_asset)/SUM(allow)*100)) total_allw_pctsat,
ROUND(DECODE(SUM(all_perm_asset), 0, 0, SUM(rqmt)/SUM(all_perm_asset)*100)) perm_rqmt_pctutl,
ROUND(DECODE(SUM(all_perm_asset), 0, 0, SUM(allow)/SUM(all_perm_asset)*100)) perm_allw_pctutl,
ROUND(DECODE(SUM(total_asset), 0, 0, SUM(rqmt)/SUM(total_asset)*100)) total_rqmt_pctutl,
ROUND(DECODE(SUM(total_asset), 0, 0, SUM(allow)/SUM(total_asset)*100)) total_allw_pctutl,
SUM(coarse_screen_asset) coarse_screen_asset,
SUM(total_excess) total_excess,
SUM(total_deficit) total_deficit,
SUM(perm_excess) perm_excess,
SUM(perm_deficit) perm_deficit,
SUM(all_perm_excess) all_perm_excess,
SUM(all_perm_deficit) all_perm_deficit,
SUM(temp_excess) temp_excess,
SUM(satisfy_rqmt) satisfy_rqmt
FROM summary_tab_dd
GROUP BY fcg, year, fcg_desc,
fac, efr, fac_desc, efr_desc,
ums_round, fcg_allow_drillable;
sql plus> log in as parsing schema user (not APEX_PUBLIC_USER)
sql plus> SELECT fcg, year, fcg_desc,
SUM(perm_asset) perm_asset,
SUM(perm_excess) perm_excess,
SUM(perm_deficit) perm_deficit,
SUM(all_perm_excess) all_perm_excess,
SUM(all_perm_deficit) all_perm_deficit,
SUM(temp_excess) temp_excess,
SUM(satisfy_rqmt) satisfy_rqmt
FROM summary_tab_dd
where year=2007
GROUP BY fcg, year, fcg_desc;
--execution plan
SELECT STATEMENT     ALL_ROWS     12     291     17460
HASH(GROUP BY)          12     291     17460
MAT_VIEW REWRITE ACCESS(FULL) RPLANSWEB.MV_FCG_ALL_SUMMARY_TAB     ANALYZED     11     291     17460                         "MV_FCG_ALL_SUMMARY_TAB"."YEAR"=2007
--execution plan from sql workshop (application express)
SELECT STATEMENT 42,341 55 3,882 1,990,027
HASH GROUP BY 42,341 55 3,882 1,990,027
TABLE ACCESS FULL SUMMARY_TAB_DD 109,158 47 3,329 5,130,426 "YEAR" = 2007
--execution plan from an APEX page (displayed from v$sql and V$SQL_PLAN)
OPERATION: SELECT STATEMENT OPTIONS: OBJECT_NAME: OBJECT_ALIAS: OBJECT_TYPE: OPTIMIZER: ALL_ROWS SEARCH_COLUMNS: 0 COST: 4600 CARDINALITY: BYTES: CPU_COST: IO_COST: ACCESS_PREDICATES: FILTER_PREDICATES: PROJECTION:
OPERATION: HASH OPTIONS: GROUP BY OBJECT_NAME: OBJECT_ALIAS: OBJECT_TYPE: OPTIMIZER: SEARCH_COLUMNS: 0 COST: 4600 CARDINALITY: 109158 BYTES: 8732640 CPU_COST: 549150132 IO_COST: 4569 ACCESS_PREDICATES: FILTER_PREDICATES: PROJECTION: "FCG"[VARCHAR2,6], "FCG_DESC"[VARCHAR2,15], SUM("PERM_DEFICIT")[22], SUM("PERM_EXCESS")[22], SUM("SATISFY_RQMT")[22], SUM("TEMP_EXCESS")[22], SUM("ALL_PERM_EXCESS")[22], SUM("ALL_PERM_DEFICIT")[22], SUM("PERM_ASSET")[22]
OPERATION: TABLE ACCESS OPTIONS: FULL OBJECT_NAME: SUMMARY_TAB_DD OBJECT_ALIAS: SUMMARY_TAB_DD@SEL$1 OBJECT_TYPE: TABLE OPTIMIZER: SEARCH_COLUMNS: 0 COST: 3329
as you can see while executing the script in sql developer the optimizer is finding the relevant materialized view, not in the case of APEX's SQL Workshop or Page.
appreciate your time

Material Revers with 262

Dear Guru,
i have one scenario we create one Maintenance order with one components material after that issued the material with full quantity against PM order or reservation now when i want to revers some qty with T CODE MB21 and movement type 262 system appear below error.
Manual reservation for order category 30 not allowed
Message no. M7126
Waiting your fast response.
Regards
Aamir

Hi,
MBRL is absolutly differ from MIGO, In MIGO it is cancellation instead here it is return of the unused material or in any case if you want to return material either fully or partially i.e. if you issue 5 materials you can return whole 5 or 2 or 3 qty. & it will also reflect in your order.
If you are returning in ref of issued mat docs no. it means against that issue you are returning the material. Its the std process.
Regards,
Anisha

Add the budget profile in the order type Maintenance Order

Dear Experts,
Scenario for Repair & Maintenance with only MM & FICO module live w.e.f. 2007 (PM not live)
Process Managed thru Internal Order (Order Type: RPMT)
Budget managed through Investment Management (IM); Budget is directly entered against the IO using transaction IM52
Scenario for Repair & Maintenance with only MM, FICO & PM module live (PM went live in 2010)
It was proposed to assign budget against each Maintenance Order. Since the number of maintenance orders being used is very high, it was decided to link the MO & IO so that budget will be assigned to the IO and when the MO is settled against the IO, the budget in IO can be deducted accordingly. The proposed process to assign budget in Internal Order against each Maintenance Order are given below-:
1.) In EAM process one can plan/procure material and External Services only when the Maintenance Order is created & released but practically it has to be planned long before any Maintenance Activity (Maintenance Order to be linked with the estimate so that PO can be created against the estimate).
2.) The no. of Maintenance Order generated in EAM Module is very large as Maintenance order is created for almost each and every maintenance activity. It is cumbersome to allocate the budget to each and every maintenance order. There should be a single estimate for maintenance activity (as in MM module) and that should be linked to maintenance order so that the actual cost of Indent/Service Entry Sheet can be deducted automatically from the estimate (Maintenance Order is to be linked with estimate).
3.) While doing return Indent the cost of return material is not being added to the maintenance order automatically (Maintenance Order is to be linked with estimate).
4.) If Material & External Services not planned in the maintenance order (estimate), the user must be able to do that through Internal Order (estimate), hence the Internal Order must be link to the Maintenance Order. They should able to record the planned & actual cost in the maintenance Order.
Process followed:
1.) Created Internal Order in KO01 for Repair & Maintenance Order Type
Assigned budget to Internal Order thru IM52
2.) Created PM order and assigned Internal order against Settlement Order in tab
u2018Locationu2019 and in Settlement Rule with 100%. In this Section attach the Internal
Order with selection type u2018ORDu2019.
3.) Released both orders and issue the Material for particular Operation and then
determine the Cost for material .After that performed MIGO for consumption of
materials.
4.) Settled the PM order in KO88.
Settlement process was successfully saved.
Problem faced:
After posting the goods movement (against each Maintenance Order) and settlement of the maintenance order against IO, we still find the budget assigned to the IO is not consumed/deducted.
1. Actual cost of maintenance is not reflected in the internal order
immediately. We have to run cost settlement (t-code KO88) for the
maintenance order each time the actual cost is incurred in the maintenance order.
2. Also in the case of return indent, the value of returned material is not directly
added to the available budget of internal order.
3. When the material is issued from store through the reservation generated by
maintenance order, system does not check for budget in the internal
order/maintenance order while issuing material from the store.
4. It must not be allowed to create reservation from the internal order of order type
RPMT.
5. In case of external service in the maintenance order, the unit of
measure in the requisition is set to u201CD (days)u201D by default. System does not allow
changing the unit of measure in the requisition (it should allow to change the unit
of measure or set the unit of measure u201CJOBu201D).
6.) When the material is issued from the store through reservation generated in
maintenance order, system does not check for budget in Internal Order
(estimate)/Maintenance Order while issuing material from store.
7.) My first problem is every time running the cost settlement(KO88) is maindetory.Without running cost settlement, How we can settle the actual amount of MO with IO (Estimate budget).
2.) As you know that I have assigned the budget in IO.How system will check the budget while issuing the goods for maintenance order.So will please tell me that which user-exit is used over here.
Thanks & Regards,

Hi Deepak1103,
Well, obviously you will have to settle the costs incurred at the maintenance order. The internal order should be mentioned in the settlement order field in the location tab of the maintenance order. What you can do is to ask your ABAP person to activate this enhancement IWO10004: Maintenance order: Customer check for order completion, use the CAUFVD structure to get the internal order number, then use the BAPI BAPI_INTERNALORDER_GETDETAIL and pass the details to the function module BBPG_BUDGET_CHECK and check the actual cost against the required budget. In case of a conflict raise an error other wise run the function module CK_F_IH_ORDER_SETTLE to settle the costs of the maintenance order to the internal order. Budget would also be consumed and you can verify the same in S_ALR_87013019.
Regards,
Muhammad Usman Kahoot

Best way to pre-populate material variable with values for users

Hi, I have a requirement to prepopulate a material variable with about 5 materials and that is the materials that will default when the query is called. The users would also need the ability to change those values.
My thought is to create a User-exit variable that derives the values from a user maintained table (infoobject).
Does anyone else have any suggestions or ideas on the best way to handle this?

I don't know if there is a best solution...
Infoobject
With this option you have to create a new infoobject (ZMATERIAL) without attribute (you need only a list material codes) and then to set the authorization profile for the user in order to manage the content.
The creation of an infoobject corresponds to a table creation, but you don't need any other specific options that belong to the infooject (as technical object)...
Table
With this option you have to create a Z table with only one field and then to allow the maintenance of the table by SM30....
In the ending, if you want to be a purist use the table, otherwise use an infoobject (but there are no significant differences !
Bye,
Roberto

Material Manufacturing with in the Workshop of Maintenance Department

Similar Messages

Maybe you are looking for